You can have a look to ivy as well. Every module can be published to a repository. Every module can pick up its dependencies from this repository and if required you can write a master build that build the submodules in the right order.
Gilles > -----Original Message----- > From: Joe Schmetzer [mailto:[EMAIL PROTECTED] > Sent: mardi 27 novembre 2007 16:50 > To: Ant Users List > Subject: Re: Handling multiple subproject in J2EE app > > Here's the technique I use in these situations: > > http://www.exubero.com/ant/dependencies.html > > Cheers, > Joe > > On Tue, November 27, 2007 3:23 pm, 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? > > > > -- > > Dimitris Mouchritsas > > Computer Services > > > > > > --------------------------------------------------------------------- > 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]
