Remove processing of dart code, summary.dart, simplified info.dart

pkg/polymer/test/run.sh

Index: pkg/polymer/test/run.sh
diff --git a/pkg/polymer/test/run.sh b/pkg/polymer/test/run.sh
index 235b6b43db4710aeecc0cc923e9faaddb1200d4e..6f0640f0f04c462fbc47c313cf822c77879a5c28 100755
--- a/pkg/polymer/test/run.sh
+++ b/pkg/polymer/test/run.sh
@@ -70,7 +70,10 @@ function compare {
 }
 
 if [[ ($TEST_PATTERN == "") ]]; then
-  echo Analyzing compiler for warnings or type errors
+  echo Analyzing analyzer for warnings or type errors

[Jennifer Messerly, 2013/08/28 22:10:25]

do we need to analyze the analyzing analyzer too?

[Siggi Cherem (dart-lang), 2013/08/29 00:34:15]

:-)

mmm... actually it might not be a bad idea. When the analyzer was reporting
transitive warnings from other packages, it used to show warnings from
analyzer_experimental, ... maybe we should add a test for it in the repo =)

+  $dartanalyzer --hints --fatal-warnings --fatal-type-errors lib/dwc.dart
+
+  echo Analyzing deploy-compiler for warnings or type errors
   $dartanalyzer --hints --fatal-warnings --fatal-type-errors lib/deploy.dart
 
   echo -e "\nAnalyzing runtime for warnings or type errors"