ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy-Lambert <>
Subject Re: Project Build Strategy Question:
Date Sat, 15 Apr 2006 03:04:46 GMT
Hello Res,

Ant is primarily a monoproject build tool.

You can look at :

   - creating your own custom system to manage dependencies using ant,
   - use Ivy [1] (referenced in the ant documentation under "External
Tools and Tasks" [2]
   - decide that ant itself should not manage multiproject dependencies
and use Maven [3]
   - use Gump [4] (which is a continuous integration/build tool) with a
model to define dependencies between projects

AFAIK Maven is a build tool which works for both developers and build
managers. It has a concept to store build artifacts in a repository
accessible via http.
I have never used Maven myself directly, I wonder whether it can do
recursive make. AFAIK it is primarily a mono project build tool (and
project management tool)
which uses among other things ant. Maven has a concept of project

You can even combine gump and maven. You can use gump as a tool to build
your complete stack of projects, and make gump invoke maven.

Gump and ant can also be combined.

In anycase, I would encourage you to use an existing framework to
describe what are the artifacts of your projects and what do they depend







Res Pons wrote:
> I have about 9-10 different projects automated under Anthill OS
> nightly.  I set up a property sheet for each project where I call
> speicific targets out their respective build.xml to generate war
> files, etc.  I have not declared any project dependencies as they're
> not needed at this point -- only two projects depend on each other and
> I fake it by building them in time order.  Then a master build.xml
> file kicks in as the last build of the night, packages the war and
> necessary jar files, checks in the files which have been modified, and
> tags all the projects in the repository by committing the local
> working folders under Anthill into Subversion and finally it deploys
> the war files to the servers for QA testing, etc.
> Is this a good strategy?  Any suggestions or feeback? Thanks.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message