in my approach I use 2 kinds of "global" files: one category is for shared properties and targets, these files contain the real smarts of your build, - such files are included by individual project build.xml files using normal XML ENTITY include, so the build.xml's are dumb - just a bunch of <property> sets & includes,
then there are global "drivers" - buildfiles which are used to invoke a series of individual build.xml's, these usually also dumb - just a bunch of <ant> calls dynamically chosing what to run is done with setting (or not) a property and then putting a condition on a target ( <target name="dowork" if="dowork.enabled" ... /> ) hope it helps, ~Alexei > -----Original Message----- > From: ravi appala [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 4:30 PM > To: Ant Users List > Subject: How to break up file-build.xml and execute them together as > optional > > > I would like to know the way to compile pieces with > individual (pices of)build.xml and also all of them > together with option by selecting them dynamically. > > I am using Ant to build and deploy for our system.We > are expanding our Web App Server to run with 20 java > applications. > I would like to create a build.xml for each > application and one global.xml with choosing each > build.xml of each application as demand and run it.How > could I do this? > > Thanks, > ravi > > ===== > Thanks, > RAVI KUMAR APPALA > > __________________________________________________ > Do you Yahoo!? > Yahoo! Web Hosting - Let the expert host your site > http://webhosting.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
