On Dec 8, 2008, at 11:34 AM, Sean Owen wrote:
I agree I don't like two build systems. I have never really gotten
into maven myself, but I have had only passing familiarity with it. I
always seem to need to do something a little tricky in the build which
only Ant will support, given that it's the more general tool (but with
disadvantages too), and so, having Ant in place, that pretty much
argues against maven because I can't justify the second build system.
You actually don't need Ant w/ Maven. You can get the Ant plugin for
Maven, which allows you too hook in Ant for doing the things Ant is
good at when you need to handle those edge cases.
I've gone back and forth a lot on Maven. Used to love it. Then was
annoyed with it. Now, I honestly think the strongest thing going for
it is you can point your IDE at the POM and it can slurp in the whole
project w/ no setup whatsoever. It's very compelling for newbies
wanting to develop and those of us who have 5+ checkouts of the same
SVN tree. Also, since it is Apache, I think it has a good
understanding of what an Apache release needs to be.
Last, but not least, the repo is the most compelling reason. Right
now, in order to publish to the repo we need have these POMs laying
around for just that purpose, but then they get out of sync. I think
I'll take a crack at seeing what is missing between Maven to Ant and
report back where the gaps are.
Yes, there is this plugin system which can bridge the gap with some
work.
I could be convinced otherwise, but at the moment my gut is that I am
not seeing enough value to switch to really feel compelled to support
it.
On Mon, Dec 8, 2008 at 4:14 PM, Grant Ingersoll
<[EMAIL PROTECTED]> wrote:
I've traditionally been resistant to Maven, but am now thinking
maybe we
should just go that route and use the Ant plugin when we need to.
I really
don't like having two build systems, esp. since they slip out of
date so
easily.
Thoughts?
-Grant
