Although CC does have a fixed set of arguments, you can add additional arguments for a given project so they can change.
For using the -lib argument, what I am trying to do is to build an environment where all extra libraries for building and testing can be kept in the CVS repository with the project. Since I am using a bootstrap build file, after I checkout the new jar files, I want to be able to kick off an Ant build using the new jar files. The only way that I seem to be able to do this since the Ant task does not take a classpath is to use the exec task. To do this, I need to have the original arguments to Ant to call the new instance of Ant. Chris Erskine EDS Consulting Services F5-EDS-001 2424 Garden of the Gods Rd Colorado Springs, CO 80919 Phone: 719-265-5962 > -----Original Message----- > From: RADEMAKERS Tanguy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 14, 2004 4:03 AM > To: Ant Users List > Subject: RE: Ant library paths > > Hi Chris, > > Sorry for the late reply, i was out sick. > > I don't know if/how ant can find the command line arguments that were used > to invoke it (i tried looking for env.ANT_CMD_LINE_ARGS > but no joy) but i wonder why you would need it: > > - If you don't know the command line args used to call ant for a given > project, i assume that means that they (the args) differ from > project to project. > - If the args differ from project to project, i assume that means that > cruisecontrol lets you script/specialize the ant call for a > given project. > - If you can do that, why can't you just pass the "-lib" switch to ant > when you call it? Unless you use ant to check stuff out of > cvs in the first place... > > I've never used cruisecontrol, so please educate me if my assumptions are > wrong... > > /t > > >-----Original Message----- > >From: Erskine, Chris [mailto:[EMAIL PROTECTED] > >Sent: Friday, December 10, 2004 11:43 PM > >To: Ant Users List > >Subject: RE: Ant library paths > > > >Is there a way within Ant to find the arguments that were > >supplied so that I > >can call a new version of Ant through the Exec task? > > > >Chris Erskine > > > >EDS Consulting Services > >F5-EDS-001 > >2424 Garden of the Gods Rd > >Colorado Springs, CO 80919 > > > >Phone: 719-535-6064 > > > > > >> -----Original Message----- > >> From: RADEMAKERS Tanguy [mailto:[EMAIL PROTECTED] > >> Sent: Friday, December 10, 2004 11:35 AM > >> To: Ant Users List > >> Subject: RE: Ant library paths > >> > >> Hi Chris, > >> > >> You could try using the <exec> task and specifying the -lib switch. > >> > >> Regs, > >> /t > >> > >> >-----Original Message----- > >> >From: Erskine, Chris [mailto:[EMAIL PROTECTED] > >> >Sent: Friday, December 10, 2004 7:23 PM > >> >To: Ant Users List > >> >Subject: RE: Ant library paths > >> > > >> >I am planning on version controlling them as part of the > >> >project. The issue > >> >is that I need an Ant task from within Ant that will allow me > >> >to add the > >> >jars to the top level classloader when I spawn ant to the new > >> >build file. > >> >The jars may not be around on the first pass or will at least > >> >be nuked and > >> >recreated when I reload the project. > >> > > >> >Chris Erskine > >> > > >> >EDS Consulting Services > >> >F5-EDS-001 > >> >2424 Garden of the Gods Rd > >> >Colorado Springs, CO 80919 > >> > > >> >Phone: 719-535-6064 > >> > > >> >> -----Original Message----- > >> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >> >> Sent: Friday, December 10, 2004 11:14 AM > >> >> To: Ant Users List > >> >> Subject: Re: Ant library paths > >> >> > >> >> 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] > >> > > >> > >>--------------------------------------------------------------------- > >> >To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]