Sam Ruby wrote:
>
> It's been that way nearly forever. When I last looked at it, the problem
> was that the javac task didn't put the classes into a separate directory so
> that the generated classes are in the current directory. This affects
> means that they are picked up in the test that tries to verify classloader
> semantics which complains.
>
> I tried to contact the owners of junit, but never got a response. More
> recently, a new developer on the junit team did comment on this, but I
> didn't follow up sufficiently to provide details.
>
> - Sam Ruby
>
Sam,
the following patch works for me when building junit. I haven't tested
any dependent projects yet - time for bed - so you may want to give a
trial run first up.
Conor
Index: project/junit.xml
===================================================================
RCS file: /home/cvspublic/jakarta-alexandria/proposal/gump/project/junit.xml,v
retrieving revision 1.8
diff -3 -u -w -p -r1.8 junit.xml
--- project/junit.xml 27 Oct 2001 14:57:17 -0000 1.8
+++ project/junit.xml 27 Feb 2002 14:16:14 -0000
@@ -13,7 +13,8 @@
</ant>
<depend project="bootstrap-ant"/>
<depend project="xml-xerces"/>
- <work parent="junit/tests/test.jar"/>
+ <work parent="dist/junit"/>
+ <work parent="dist/junit/junit.jar"/>
<home parent="dist/junit"/>
<jar name="junit.jar" id="junit"/>
<javadoc parent="dist/junit/javadoc"/>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
