Cleaning up unittest configurations

pkg/unittest/lib/vm_config.dart

 // Copyright (c) 2012, 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.
 
 /**
  * A simple unit test library for running tests on the VM.
  */
 library unittest_vm_config;
 
 import 'dart:io';
 import 'unittest.dart';
 
-class VmConfiguration extends Configuration {
-  void onDone(int passed, int failed, int errors, List<TestCase> results,
-      String uncaughtError) {
+class VMConfiguration extends Configuration {
+  void onDone(bool success) {
     try {
-      super.onDone(passed, failed, errors, results, uncaughtError);
-    } on Exception catch (ex) {
+      super.onDone(success);
+    } catch (ex) {
       // A non-zero exit code is used by the test infrastructure to detect
       // failure.
       exit(1);
     }
   }
+
+  void notifyController(String msg) {}
 }
 
-void useVmConfiguration() {

[Jennifer Messerly, 2013/01/10 03:01:18]

totally optional but: is it worth having an @deprecated forward for this method,
and remove after this build goes out?

(guessing a decent number of people are using unittest, so they might be calling
this method)

-  configure(new VmConfiguration());
+void useVMConfiguration() {
+  configure(new VMConfiguration());
 }