Prepare to publish analyzer, front_end, and kernel.

pkg/kernel/pubspec.yaml

Index: pkg/kernel/pubspec.yaml
diff --git a/pkg/kernel/pubspec.yaml b/pkg/kernel/pubspec.yaml
index 6d330b73372933b249d8fad8e58cd78e078f17eb..65ceb4d74d940d5029a865fe4394f5985bf2664f 100644
--- a/pkg/kernel/pubspec.yaml
+++ b/pkg/kernel/pubspec.yaml
@@ -11,7 +11,8 @@ dependencies:
   logging: ^0.11.2
   package_config: ^1.0.0
 dev_dependencies:
-  analyzer: ^0.30.0-alpha.0
+  analyzer: ^0.30.0-alpha.3
+  front_end: ^0.1.0-alpha.2
   test: ^0.12.15+6

[asgerf, 2017/04/21 08:25:56]

Did you check that "pub get" works? 

The test package depends on analyzer, and this dependency usually conflicts with
the -alpha.x version dependency.

Should we just not declare our dev_dependencies in the first place? AFAIK there
is no way to develop kernel outside of the SDK.

[Paul Berry, 2017/04/21 08:34:57]

Unfortunately, due to the tight coupling, there's a chicken-and-egg problem:
"pub get" won't work until after all the related packages are published.  For
instance, if I run it right now in pkg/kernel, it says:

Package analyzer has no versions that match >=0.30.0-alpha.3 <0.31.0 derived
from:
- kernel depends on version ^0.30.0-alpha.3

But that should go away as soon as analyzer is published.

My usual approach is to do my best to get the dependencies right in the first
place, and then if I'm wrong, I bump the versions again and retry.
Yeah, that's another reason "pub get" isn't going to work, even after
publishing.  Usually what we do is ask Bob to widen test's dependency on
analyzer after publishing, at which point things start working because now there
is a version of test out there that satisfies the constraints.
That's a really good point.  I'll open up an email discussion about that.

   stack_trace: ^1.6.6
   ansicolor: ^0.0.9
@@ -19,5 +20,3 @@ dev_dependencies:
     git:
       url: https://github.com/peter-ahe-google/testing.git
       ref: 2e196d5
-dependency_overrides:
-  analyzer: {path: ../analyzer}