From b192abe36edcf2f303a92a7a1e7f0c9973bc9f3f Mon Sep 17 00:00:00 2001
From: Ben Hale <bhale@vmware.com>
Date: Tue, 11 Sep 2007 14:50:10 +0000
Subject: [PATCH] On second thought, failing quickly doesn't make sense for CI
 builds.

---
 common-build/common-targets.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common-build/common-targets.xml b/common-build/common-targets.xml
index ddcd9308..ef956fc9 100644
--- a/common-build/common-targets.xml
+++ b/common-build/common-targets.xml
@@ -870,7 +870,7 @@
          we want to optionally run all tests and report on the whole
          batch, then we need to set a failure property as in the server
          tests. -->
-    <junit forkmode="perBatch" printsummary="yes" haltonfailure="yes" haltonerror="yes"
+    <junit forkmode="perBatch" printsummary="yes" haltonfailure="no" haltonerror="no"
                     dir="${basedir}">
       <jvmarg value="${unitvm}" />
       <jvmarg value="-Djava.security.auth.login.config=${target.testclasses.dir}/auth.conf" />