tree 13a760cf361d74cc8cd831b87c98469ccfff5a77
parent 42be7e0387caebf9275be05582168e9438da5960
author Elliot Glaysher <erg@chromium.org> 1425939584 -0700
committer Elliot Glaysher <erg@chromium.org> 1425939584 -0700

Run dartanalyze on the dartzip file structure, by default.

This patch relands b905249b657b3ff373878a8756e2bde47e1289e6, which
enabled running dartanalyze by default, and hopefully fixes the problems
seen in that first run:

Instead of setting --package-root to the current build's out/.../gen/
dir, after building the dartzip file, unzip it to a temporary directory
and then run the analyzer on that.

a) This allows us to check that all dependencies are actually expressed
   in build rules.

b) This lets us run the dartanalyze in other repositories. (We may be
   consuming dartzips in repository B which were generated in repository
   A.)

c) This keeps us from being tied to the build output of one repository.

BUG=459376
R=tonyg@chromium.org, zra@google.com

Review URL: https://codereview.chromium.org/996483003