Personally, I managed multi-project dependencies in Ant using the technique described at http://www.exubero.com/ant/dependencies.html (though any of the other tools are suitable solutions, as well).
Although CruiseControl can handle multiple projects, it doesn't necessarily understand project dependencies very well (though you can fake it with the CC <buildstatus> config element - see http://cruisecontrol.sf.net/main/configxml.html#buildstatus ) Cheers, Joe On Sat, 2006-04-15 at 05:55 -0400, nikhil wrote: > Cruise Control is also used for this purpse and many of the people that I > know that have used it swear by it. It invokes ant. > Nikhil > ----- Original Message ----- > From: "Antoine Levy-Lambert" <[EMAIL PROTECTED]> > To: "Ant Users List" <user@ant.apache.org> > Sent: Friday, April 14, 2006 11:04 PM > Subject: Re: Project Build Strategy Question: > > > > 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 > > descriptor. > > > > 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 > > upon. > > > > Regards, > > > > Antoine > > > > [1] http://ivy.jayasoft.org/ > > > > [2] http://ant.apache.org/external.html > > > > [3] http://maven.apache.org/ > > > > [4] http://gump.apache.org/ > > > > 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: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Joe Schmetzer .:. Renaissance Developer .:. http://www.exubero.com/ +44-(0)7775-770-422 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
