I'm not particularly opposed to it, but I'm not exactly for it
either. I very much have a love hate relationship with Maven. The
simple things work fine w/ Maven and the power of pointing Eclipse or
IntelliJ at a POM file and having the whole project imported and ready
to work on w/o one iota of setup is something that the proponents of
Ant just don't get, especially when it comes to multiple module builds
like Solr and Lucene have. That being said, there are a lot of
headaches with Maven, number one being releases, number two being
anything custom and number three being the constant instability of the
magic happening behind the scenes with it upgrading dependencies, etc.
automatically. Finally, I've always had a hard time getting help in
Maven land. It always seemed to me the number of incoming questions
outweighed the number of answers about 10 to 1.
I converted Mahout to Maven and it was a pain. I also use Maven for
personal development as well. It is much easier to start fresh on
Maven than it is to add it in later. And, there is something to be
said for the Maven Ant plugin, but even that is clunky.
In the end, I think I'd be +0 on it. It's also come up in the past on
the lists and there never is a clear consensus.
-Grant
On Jun 28, 2009, at 12:33 PM, aldana wrote:
hi,
are there plans to migrate from ant to maven2? maybe not for the
current
trunk (mainline for 1.4), but maybe for the trunk after releasing
solr 1.4.
it makes the build more standard and easier to import to IDEs.
-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
--
View this message in context:
http://www.nabble.com/plans-for-switching-to-maven2-%28after-1.4-release%29--tp24243036p24243036.html
Sent from the Solr - User mailing list archive at Nabble.com.
