Well, you could version-control your libraries and get them out based on
version and project..
ant lets you specify wildcards, you could simply get out all your
libraries, and include them with a mask like:
../lib/*.zip
../lib/*.jar
Edward Wittmann
"Erskine, Chris" <[EMAIL PROTECTED]>
12/10/2004 12:47 PM
Please respond to "Ant Users List"
To: [EMAIL PROTECTED]
cc:
Subject: Ant library paths
I have seen a number of mails about the ant runtime path for items like
the
optional jar files. The environment that I am working with is running
under
CruiseControl, I am calling a build file that will delete the project
directory and then recreate it. In this project, I want to have an ant
lib
directory that will contain the jars that are required for running ant.
The
question is how to spawn ant from the first build file passing in the jars
in this lib directory and include all of the arguments that are passed to
the first instance of ant?
I want to do it in this form to allow me to have multiple projects that
may
be dependent on different version of the optional jar files so that I am
not
required to upgrade all the projects at the same time when a new version
of
a jar becomes available.
Chris Erskine
EDS Consulting Services
F5-EDS-001
2424 Garden of the Gods Rd
Colorado Springs, CO 80919
Phone: 719-535-6064
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
