I have recently commented on a blog "Why do you Hate Maven?", let me
cite myself ;-)
"I was first confronted with maven when I tried to understand
the building of an OS project [that was Jetspeed2]. That's
when I started hating it, because it took me days to find out.
There is no simple introduction. I didn't want to buy a
philosophy, I just needed a different packing of a jar. Had
it been ant, this would have been a matter of minutes."
If there is the opportunity to get maven out of Jetspeed2, seize it and
hold tight!
Looking at the referenced mail
(http://mail-archives.apache.org/mod_mbox/portals-jetspeed-dev/200602.mbox/[EMAIL
PROTECTED])
I can hardly see any trade-offs: the only "con" for ant is that "Ant
build.xml files can become unmanageable." This is true. But as I know
from experience, this can be overcome if you carefully design the build
system, especially the hierarchy.
Regards,
Michael Lipp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
