I guess I need to start reading on Ivy then... While playing around with Joe's solution I managed to put ant in an infinite loop. My worst fear is that I won't be able to persuade my manager to start using Ivy. Currently we do our build in a horrendous and huge, over 1500 line, build file.
On Nov 27, 2007 6:43 PM, Steve Loughran <[EMAIL PROTECTED]> wrote: > Dimitris Mouchritsas wrote: > > Hi all, I'm trying to figure out what's the best way to handle a J2EE > > project with different modules. > > I'm thinking to create a sub project structure a bit like Maven but have > ant > > build files. I can handle > > each project separately easily. My problem is interconnecting the > > sub-projects. For example I would > > like, when compiling the war servlet classes to depend on the EJB jar > being > > up to date. So I would like > > to use a master build file but have each sub-project understand its > > dependencies. Are there any best > > practices that you know of? > > > > Ivy. Every sub project publishes their artifacts; the next things down > the chain pulls them in. Ivy can also generate an order for build files > that takes the dependencies into account. > > > -- > Steve Loughran http://www.1060.org/blogxter/publish/5 > Author: Ant in Action http://antbook.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Dimitris Mouchritsas Computer Services
