Summary: | JUnitTask does not include its codebase in forked command line | ||
---|---|---|---|
Product: | Ant | Reporter: | Scott M Stark <Scott_Stark> |
Component: | Optional Tasks | Assignee: | Ant Notifications List <notifications> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | notifications |
Priority: | P1 | ||
Version: | 1.3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Scott M Stark
2001-04-05 20:24:18 UTC
I don't think we should implicitly add Ant's runtime classes to the classpath for <junit> - some things work if you run junit forked but not if you run things in VM, just because we don't include everything from ANT_HOME/lib (tests that require a different XML parser for example). If we had a way to only include the classpath entries that contain the junit task and junit.jar itself, fine. But this may be difficult to find out - I'll investigate this a little. You cannot rely on the task being defined in optional.jar. Finally, you should get a running fork="true" version, if you give a nested classpath element to <junit> that contains all required classes. fixed for JDK > 1.1 starting with nightly build 2001-07-13 |