> So, the proposal would be to change this to the following:
>
> commons-collections.jar=${lib.repo}/commons-collections.jar
> commons-logging.jar=${lib.repo}/commons-logging.jar
> junit.jar=${lib.repo}/junit.jar
>
> right? You would rely on the user to define their own
> lib.repo property
> someplace if they are using this approach.
That catch is, which junit.jar are you talking about? The configuration
information is completely lost. Junit's MANIFEST.MF doesn't carry the
information. That's suboptimal, but needs to be taken up with the junit
project. Creating a jakarta version of junit is a way to madness.
OK, you can actually tell the difference between junit distributions by
examination of the contents of the jar. Their build process leaves some
cruft, such as build.xml and a junit3.7 directory. But that's not really
reliable. And there are probably other cases out there.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
