Jason:
I just checked my system here and I have JUnit in lib/ext so naturally I didn't see the problem you are experiencing. Yes - junit needs to be included in the jar dowloading stuff. In addition to the modification of the include.properties, you will need to inclde a reference to the junit jar file in the tools.class.path entry in the buildfile.
Cheers, Steve.
Jason Webb wrote:
I'm confused about the auto-getting of junit I also had to add the following line to build.xml <pathelement location="${junit.jar}"/> As well as add the following to include.properties # ----- junit ----- junit.jar=${lib.dir}/junit-3.7.jar
Is this correct, or am I barking up the wrong tree. With those changes I can pull down junit 3.7 if I don't have it and if I do then everything is OK
If this is correct I'll submit a patch for the other files
-- Jason
-----Original Message-----
From: Jason Webb [mailto:[EMAIL PROTECTED] Sent: 24 February 2003 09:49
To: James Developers List
Subject: [PATCH] check-targets.properties
The Maven style trick doesn't work as the Ant build adds the current version to the .id prop.
-- Jason
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
