Modify scanner and parser to be standalone packages.

pkg/dart_parser/testing.json

Index: pkg/dart_parser/testing.json
diff --git a/pkg/dart_parser/testing.json b/pkg/dart_parser/testing.json
new file mode 100644
index 0000000000000000000000000000000000000000..d25b676edef8a16a32621502fa79d7198f9f7d8f
--- /dev/null
+++ b/pkg/dart_parser/testing.json
@@ -0,0 +1,30 @@
+{
+"":"Copyright (c) 2016, the Dart project authors. Please see the AUTHORS file",
+"":"for details. All rights reserved. Use of this source code is governed by a",
+"":"BSD-style license that can be found in the LICENSE.md file.",
+  "suites": [
+    {
+      "name": "parser",
+      "kind": "Chain",
+      "source": "test/parser_suite.dart",
+      "path": "../../",

[Siggi Cherem (dart-lang), 2017/01/12 21:56:04]

It's nice that you can use the entire repo as a test suite! It however seems
brittle that anyone submitting a Dart file could technically make the test suite
fail. Is that a concern? I guess most of the time Dart files are valid and it
should be OK.

[ahe, 2017/01/13 07:16:21]

That is a big concern, and something I'll have to carefully consider before
setting up automated tests based on this.

But the great thing is that this config file could be something we just use
occasionally, or run on a separate build bot.

+      "status": "test/parser.status",
+      "pattern": [
+        "\\.dart$"
+      ],
+      "exclude": [
+        "README.dart"
+      ]
+    }
+  ],
+  "analyze": {
+    "uris": [
+      "bin",
+      "lib/",
+      "lib/src/",
+      "test/"
+    ],
+    "exclude": [
+    ]
+  }
+}