[ http://issues.apache.org/jira/browse/DERBY-2006?page=comments#action_12446783 ] Andrew McIntyre commented on DERBY-2006: ----------------------------------------
Correct, junitreport is the top-level target. About having to put junit.jar into the classpath, that's a general Ant problem, covered in this FAQ: http://ant.apache.org/faq.html#delegating-classloader-1.6 Apparently this problem has been fixed in Ant 1.7 (due out any day now) such that <junit> tasks honor their nested classpath. > Add JUnit and JUnitReport task as a target in Ant script > -------------------------------------------------------- > > Key: DERBY-2006 > URL: http://issues.apache.org/jira/browse/DERBY-2006 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.3.0.0 > Environment: Any > Reporter: Yip Ng > Assigned To: Andrew McIntyre > Fix For: 10.3.0.0 > > Attachments: derby_2006_v1.diff, derby_2006_v2.diff, > derby_2006_v3.diff, derby_2006_v4.diff, derby_2006_v5.diff, > derby_2006_v6.diff, example_output.zip > > > Ant has an optional tasks called JUnit and JUnitReport that runs JUnit tests > and produces JUnit report respectively. It will be nice to have these > mechanism incorporated into the Ant script so one can easily kick off a JUnit > test and view the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
