> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 21, 2002 12:36 PM
...
> commons-collections.jar=${commons-collections.home}/commons-co
> llections.jar
> commons-logging.home=../logging/dist
> commons-logging.jar=${commons-logging.home}/commons-logging.jar
> junit.home=/usr/local/junit3.7
> junit.jar=${junit.home}/junit.jar
>
> 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
Could you use naming conventions like:
commons-collections.jar=${lib.repo}/commons-collections_1.2.jar
to refer to the explicit version (1.2 in this case) of the jar?
Whereas, the following line:
commons-collections.jar=${lib.repo}/commons-collections.jar
would mean you're using the latest and greatest build (probably
something built off of CVS MAIN, but *not* a symlink to a
versioned jar)?
- Gidado
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
