DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=6606>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=6606 ------- Additional Comments From [EMAIL PROTECTED] 2005-05-30 21:39 ------- I have a patch that makes junit work without any changes to the ant installation. The only requirement is that you fork a new JVM for the junit test. How did I do this? I changed the ant-junit.jar so it does not load/reference any junit classes before it forks a new JVM. That way the classloader problems disappear since junit classes are not loaded inside ant's JVM. If you want to give it a testspin, get the jar file here: 1) Download ant-junit.jar from here http://tobiasen.dk/ant/ant-junit.jar 2) Drop it in $ANT_HOME/lib 3) Run your tests, remember to set fork="yes" in your tests and have the junit.jar in the classpath of the test. <junit fork="yes" printsummary="yes"> <classpath> include junit.jar here... </classpath> ... I have compiled the ant-junit.jar using jdk 1.4.2_08 and against ant 1.6.4. I would like to submit the patch, but I have no experience in submitting patches. Please tell me how. The patch is quite big, since almost all classes in org/apache/tools/ant/taskdefs/optional/junit are changed and I have introduced some new interfaces. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
