Re: 3.8 candidate

Here we see the dangers of running a subset of the whole suite. We 
only ran the tests for the new string diff code, and forgot to run 
the whole suite before checking in. It'll be fixed tonight.

The problem with the unstable test is timing related and I'll also 
fix that.

Kent

--- In junit@xxxx, Mike Clark <mike@xxxx> wrote:
> There also seems to be a compatibility issue with the JUnit 3.8 
> candidate and the current version of the JUnit task for Ant:
> 
> test:
>     [junit] java.lang.NoSuchMethodError
>     [junit]     at 
> org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResult
> Formatter.startTest(PlainJUnitResultFormatter.java:188)
>     [junit]     at junit.framework.TestResult.startTest
(TestResult.java:151)
>     [junit]     at junit.framework.TestResult.run
(TestResult.java:103)
>     [junit]     at junit.framework.TestCase.run(TestCase.java:122)
>     [junit]     at junit.framework.TestSuite.runTest
(TestSuite.java:208)
>     [junit]     at junit.framework.TestSuite.run(TestSuite.java:203)
>     [junit]     at junit.framework.TestSuite.runTest
(TestSuite.java:208)
>     [junit]     at junit.framework.TestSuite.run(TestSuite.java:203)
>     [junit]     at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.
> run(JUnitTestRunner.java:231)
>     [junit]     at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.
> main(JUnitTestRunner.java:409)
>     [junit] Exception in thread "main"
> 
> 
> Mike