The latest update to analyzer_cli makes it analyze all files using a
single context, so it can re-use analysis results; this makes it much
faster when analyzing large projects (~13x faster at analyzing pub,
for example).
On a temporary basis, this CL pulls in analyzer_cli using a git SHA
rather than a tag, since the new analyzer_cli features don't have a
release tag yet. Once they have been validated on the buildbots, I'll
assign a release tag and update DEPS to point to it.
R=pquitslund@google.com
Review URL: https://codereview.chromium.org//1170543003
There are several benefits of this:
Devs and bots are pulling from the same location, so issues are easier to track down
Devs can make sure the mirrors are working locally before rolling deps
We pull from the same place for both dart-lang and community repos
R=whesse@google.com
BUG=
Review URL: https://codereview.chromium.org//1154413004
`cli_util` is consumed by *at least* dartanalyzer, the dev compiler and dartdoc. This change updates third_party to add `cli_util` and it's own deps (`when` and `which`). Note that `when` and `which` have both been transitioned to dartlang proper to ensure sanity moving forward. They're both independently useful. `which` especially for CLI tools.
Review URL: https://codereview.chromium.org//1155233002
Readd samples, samples-dev, tools/testing/bin, third_party removed by cleanup (no history, sorry)
Add DEPS file which will replace the old all.deps and standalone.deps
Add tools/deps/dartium.deps replacing the old dartium.deps (but now editable from a normal checkout)
Fixup tools/utils.py to use the new archiving schema (git count for be, version number for dev/stable
Fix codereview.settings