If your intention is to call a new build.xml rather than just calling another target use <ant> To quote Ant doc for <ant> task inheritAll attribute to false and only "user" properties (i.e., those passed on the command-line) will be passed to the new project. You can also set properties in the new project from the old project by using nested property tags These properties are always passed to the new project and any project created in that project regardless of the setting of inheritAll. This allows you to parameterize your subprojects
Creating nested property tags http://ant.apache.org/manual/CoreTasks/property.html I think thats Enough free advice for today Bye, ----- Original Message ----- From: "Erskine, Chris" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Friday, December 10, 2004 6:04 PM Subject: RE: Ant library paths > Actually, to call a new version of Ant with a new build file, it is <ant> > but it does not allow me to add extra jar files so that I can have different > versions of common jar files for each 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: Laconia Data Systems [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 10, 2004 3:55 PM > > To: Erskine, Chris > > Cc: Ant Users List > > Subject: Re: Ant library paths > > > > The agreed upon way for one build.xml to call any other Ant target is > > Antcall > > Concerning params > > I would inquire on params (which are based on properties -file based or > > otherwise ) from Antcall > > http://ant.apache.org/manual/CoreTasks/antcall.html > > HTH, > > Martin- > > > > ----- Original Message ----- > > From: "Erskine, Chris" <[EMAIL PROTECTED]> > > To: "Ant Users List" <[EMAIL PROTECTED]> > > Sent: Friday, December 10, 2004 5:43 PM > > 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] > > --------------------------------------------------------------------- > 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]
