Dimitris Mouchritsas wrote:
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:
The ant tasks for maven are very similar, but I have found them to be
-at the time I was looking at them for my book - to be of a fairly low
quality. The authors werent heavy Ant users -it was the maven team after
all- and were written with no tests, no reentrancy, and fairly weak
failure modes. Also, Ivy is way better at handling complex dependency
setups, with different paths for different custom tasks, etc. That said,
Maven profiles may achieve something similar.
The Ivy stuff doesnt need Ant, but the team all use ant, it is an apache
project under ant.apache.org these days, and we may move to tighter
coupling in future.
If you are sticking with Ant, use Ivy.
--
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]
