ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Baldry, Scot M" <>
Subject RE: recursive ant build: recommendation?
Date Mon, 11 Jun 2001 17:28:23 GMT

We currently use ANT in an environment very similar to one that you describe
in your original email. A team of approx 30 developer each use the tree to
build invidual projects that are built / tested and migrated independently
intra-day but are compiled and tested over-night. To achieve this goal I
have had to do very little work:

1. I use cascading build.xml files for example:

The above package structure contains a total of 4 build.xml files under the
following dirs:


2. I have factored out all my common targets to "buildCore.xml" that resides
at the top level. I spent quite some time putting this together but
basically most developers can now produce a build.xml file for a new project
in ~10 lines of XML!

3. I have extended the "ant" task so that I can now do things like

<ant antfile="build.xml" dir="abc/mypackage1"
ifexists="abc/mypackage1/build.xml" />

Let me know if you would like me to explain further,


-----Original Message-----
From: Ventimiglia, David []
Sent: 11 June 2001 18:07
To: ''
Subject: RE: recursive ant build: recommendation?

>I have already seen first hand what happens when a single ANT file or even
>single set of ANT files (all
>at the top level) are used to handle this kind of interrelated projects. It
>is not pretty, especially when
>combined with an "exclusive check out" revision control system...

Hi Jim,

Can you elaborate on the problems you've had using a single Ant build file?


View raw message