Here is a patch that makes this change. It is a bit hokey the way it just abruptly exits in BaseTestCase.runBare(). I suppose the cleaner way to do it is to make a TestRunner to extend junit.textui.TestRunner, but that would not be something I could check in. Anyway, please review and let me know if you object to this change or see a better way. I noticed the ant task for junit has a haltonerror and haltonfailure attributes but don't see anything for the junit.textui.TestRunner

I took a quick look at it looks reasonable to me - we'd use this option only while actively debugging, I imagine...Some comments to clarify would be nice.

Kathey, I took a look at the patch and for the purpose that it is serving, I think it is ok for it to just exit out when the first test fails with error.

Commit 1539729 from Kathey Marsden in branch 'code/trunk'
[ https://svn.apache.org/r1539729 ]

DERBY-6401 Create a test option to stop running Junit tests after first failure or error
Adds test option. If run with -Dderby.tests.stopAfterFirstFail=true tests will stop after first failure or error

Commit 1541258 from Kathey Marsden in branch 'code/branches/10.10'
[ https://svn.apache.org/r1541258 ]

DERBY-6401 Create a test option to stop running Junit tests after first failure or error

merge revision 1539829 from trunk