Thank you everyone. You've given me a lot of food for thought. From everyone's writings, if I understand correctly, the ant tasks for maven is nearly the same as ant+ivy, right? I suppose I will start looking into integrating ivy into a small example project and see what I'll get from this. From my point of view, I suppose we have a fairly standard J2EE project but should allow for flexibility (it's got a 2 year lifespan) as we don't know yet what might pop up. Once again thank you everyone.
On Nov 28, 2007 7:27 AM, Joe Schmetzer <[EMAIL PROTECTED]> wrote: > Hi Dimitris, > > If you're still having troubles with the technique at > http://www.exubero.com/ant/dependencies.html , I would recommend that > you download the example scripts mentioned at the bottom of the email > (http://www.exubero.com/ant/example.tar.gz ). Hopefully, using that as a > base, you can extend it to your situation. > > I tend to use that technique for splitting a monolithic project into > smaller, more manageable components. It's relatively simple, and doesn't > rely on any other software, just purely Ant. > > You mentioned in another post that you managed to put Ant into an > infinite loop using this technique, which sounds strange. Perhaps you > have some sort of cyclical dependency? It's hard to say without looking > at your scripts what actually happened. > > For larger build systems, I would definitely recommend looking at one of > the repository solutions: Ivy or Maven2. This sort of configuration > elegantly breaks the back of complex dependency management. To a degree, > it can even handle cyclical dependencies (though of course, you should > avoid that at all costs, anyway). > > I've heard a lot of good reports about Ivy, but I haven't used it > myself. Other people on this list are better suited to sing praises in > that direction. > > In my current company, we have settled on using Ant scripts and a Maven2 > repository with the Ant Tasks for Maven > (http://maven.apache.org/ant-tasks.html ). This enabled us to move to a > repository solution that could be shared by both Ant and Maven. We have > a number of other projects that use Maven, and this seemed the best of > both worlds. Just to be clear: I really like the Maven repository, but I > don't really care much for Maven itself, as I discuss at > http://www.exubero.com/blog/20070313_Why_I_Prefer_Ant_Over_Maven.html > > Cheers, > Joe > > On Tue, 2007-11-27 at 18:38 +0200, Dimitris Mouchritsas wrote: > > I've had a look in Joe's solution but I could not understand much yet. > > Although it seems to be exactly what I want I've difficulty grasping the > > solution. I want to take a look in Ivy as well but probably at a later > time. > > Thank you both. Joe if you could elaborate a bit on your solution... > I'll > > try to play with it a little bit to see if I can get a better grasp in > the > > meantime. > > > > On Nov 27, 2007 6:02 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote: > > > > > 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] > > -- Dimitris Mouchritsas Computer Services
