no longer require entry points to be specified in the build.dart file

pkg/polymer/lib/builder_init.dart

Index: pkg/polymer/lib/builder_init.dart
diff --git a/pkg/polymer/lib/builder_init.dart b/pkg/polymer/lib/builder_init.dart
new file mode 100644
index 0000000000000000000000000000000000000000..6cb0d82f29225e6ae28d54637cddb99485310a05
--- /dev/null
+++ b/pkg/polymer/lib/builder_init.dart
@@ -0,0 +1,12 @@
+// Copyright (c) 2013, 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 file.
+
+/// Library that defines a main which calls build() from builder.dart. For
+/// polymer projects the build.dart file can simply export this to make the
+/// linter run on all of the entry points defined in your pubspec.yaml.
+library polymer.builder.init;

[Siggi Cherem (dart-lang), 2014/09/15 21:35:20]

maybe rename the file and library to 'default_build'?

[jakemac, 2014/09/15 22:20:52]

Done.

+
+import 'builder.dart';
+
+main(args) { build(options: parseOptions(args)); }

[Siggi Cherem (dart-lang), 2014/09/15 21:35:20]

I wonder if we should just call `lint`. `build` was more useful back in the day
when we were just getting started with pub-build, and people wanted an
alternative way to build. I don't think it's used much today, and it is not that
well tested.

[jakemac, 2014/09/15 22:20:52]

Done.