Experienced the same problem. Fixed it by removing an old ant-junit.jar from the classpath.
Shawn Castrianni wrote: > > I am getting a forked JVM crash for my junit task after the unit tests run > successfully. I am using ANT 1.7. I found the report on bug 41104 which > is similar, but I never got the FileNotFoundException as described in the > bug report and I am pretty sure I don't have two different version of ANT > on my classpath. If I change my junit to a java task and specify the test > name as the main class and provide a main method that creates a suite(), > it runs fine and the forked JVM does not crash. One thing I did notice > with using a java task is that I see more output on the screen that > appears to be coming from System.err. This System.err is not visible when > running with junit task. Where is it going? I have tried versions of > formatters and such, but I can't get the forked JVM crash to go away. > > --- > Shawn Castrianni > > ---------------------------------------------------------------------- > This e-mail, including any attached files, may contain confidential and > privileged information for the sole use of the intended recipient. Any > review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive > information for the intended recipient), please contact the sender by > reply e-mail and delete all copies of this message. > -- View this message in context: http://old.nabble.com/JUnit-crash-after-successful-run-tp17224723p26933542.html Sent from the Ant - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
