Vladimir Bossicard wrote: > > I don't know if the problem was already posted but the execution of > JUnit with Gump gives the following result: > > [java] ......................................... > [java] .....................................F.... > [java] ............. > [java] Time: 4.089 > [java] There was 1 failure: > [java] 1) >testJarClassLoading(junit.tests.runner.TestCaseClassLoaderTest)junit.framework.AssertionFailedError: > Cannot find test.jar > [java] at >junit.tests.runner.TestCaseClassLoaderTest.testJarClassLoading(TestCaseClassLoaderTest.java:33) > [java] > [java] FAILURES!!! [java] Tests run: 95, Failures: 1, Errors: 0 > [java] > [java] Java Result: -1 > BUILD SUCCESSFUL > > And to my opinion the build is not successful :-) Sorry, didn't have to > much time to write a patch.
The indication that the build was successful was provided by Ant. It would be possible to change this with a change to junit's build.xml. This particular failure is a classloader issue, and is caused by junit compile it's classes into the current working directory instead of a separate directory that I can easily exclude. Again, this could be resolved with a change to junit's build.xml. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
