There are cultural issues as well as technical issues to adopting Maven.
Most folks involved with Lucene are familiar with using Ant and
maintaining an Ant-based build system. So merely converting Lucene to
be built by Maven will not cause everyone who currently works on Lucene
to become willing and able to to use Maven on a daily basis.
Long-term, we probably should not attempt to maintain two official build
systems. But, short-term, it would be useful for developers to be able
to evaluate Maven, then discussion can begin about whether the project
should switch to Maven as its primary build system.
Doug
karl wettin wrote:
15 feb 2007 kl. 20.27 skrev Erik Hatcher:
On Feb 15, 2007, at 12:10 PM, karl wettin wrote:
I would not mind introducing Maven builds in Lucene. It would solve
/at least/ this problem. And it would merge so great with my other
projects. :) I'd be happy to help out , but there are some wicked
anting going on in a lot of build.xml:s so I would probably need a
lot of help from the contributors understanding whats going on.
Most of the build scripts could be halfway housed using
maven-antrun-plugin.
I'm open to Maven builds, for the record. I'll do what I can to help
with understanding any of the wicked anting in there, but I don't know
Maven so the best I'll be able to do is explain what is going on.
The main complexity we have is the contrib area, oh and JavaCC... the
rest is straightforward stuff.
I'll see what I can do this weekend.
+++
ATH
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
