You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by aldana <al...@gmx.de> on 2009/06/28 18:33:30 UTC
plans for switching to maven2 (after 1.4 release)?
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.
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Noble Paul നോബിള് नोब्ळ् <no...@corp.aol.com>.
my -1 for a a maven only build system. Building has not been a problem
for me with Solr.
+0 to add a pom.xml as a parallel setup
On Mon, Jun 29, 2009 at 6:46 PM, Erik Hatcher<er...@ehatchersolutions.com> wrote:
> I'll weigh in and throw a -1 to a Maven-only build system for Solr. If
> there is still a functioning Ant build, but Mavenites have a parallel setup,
> that's fine by me and I'd be -0 on that.
>
> These days, Buildr has my attention as a way to get the best of all worlds:
> access to Ant's powerful task library, POM/repo handling, AND Ruby :)
>
> Erik
>
> On Jun 29, 2009, at 9:01 AM, Grant Ingersoll wrote:
>
>> 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.
>>>
>>
>
>
--
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I'll weigh in and throw a -1 to a Maven-only build system for Solr.
If there is still a functioning Ant build, but Mavenites have a
parallel setup, that's fine by me and I'd be -0 on that.
These days, Buildr has my attention as a way to get the best of all
worlds: access to Ant's powerful task library, POM/repo handling, AND
Ruby :)
Erik
On Jun 29, 2009, at 9:01 AM, Grant Ingersoll wrote:
> 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.
>>
>
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Grant Ingersoll <gs...@apache.org>.
On Jun 29, 2009, at 9:01 AM, Grant Ingersoll wrote:
>
> I converted Mahout to Maven and it was a pain.
I'd add, however, that now that it is done, it is fine, except of
course, that Maven 2.1.0 doesn't work with it apparently because of
upgrades.
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
On Tue, Jun 30, 2009 at 1:48 PM, Fergus McMenemie <fe...@twig.me.uk> wrote:
>
> I have not used Maven much but we seemed to have tons of bother
> setting it up on nodes which had no internet access. In fact I
> can state is was the key reason we did not move to cocoon 2.x.
>
>
You can setup an internal repository mirror (which is strongly recommended)
and use a organization wide parent POM which points to this repository. This
is what we do at AOL.
Coming back to the original topic, I think it is a lot of work setting up
maven to work correctly for the current project structure. Unless everybody
agrees to change that, we should just stick with Ant. No use maintaining two
build systems. We're pushing artifacts to the official repository so the
most common ask by users is covered.
--
Regards,
Shalin Shekhar Mangar.
RE: plans for switching to maven2 (after 1.4 release)?
Posted by Fergus McMenemie <fe...@twig.me.uk>.
>FWIW
>I strongly agree with your sentiments, Manual.
>One of the neat maven features that isn't well known is just being able to do "mvn jetty:run" and have Jetty load up right away (no creating of a web-app directory or packaging of a war or anything like that).
>What I hate about ant based projects is that each ant file is yet another build script to figure out. That and dealing with .jar's of course.
>
>Yeah, maven can be annoying at times.
>
I have not used Maven much but we seemed to have tons of bother
setting it up on nodes which had no internet access. In fact I
can state is was the key reason we did not move to cocoon 2.x.
Fergus.
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Noble Paul നോബിള് नोब्ळ् <no...@corp.aol.com>.
On Tue, Jun 30, 2009 at 4:50 AM, Smiley, David W.<ds...@mitre.org> wrote:
> FWIW
> I strongly agree with your sentiments, Manual.
> One of the neat maven features that isn't well known is just being able to do "mvn jetty:run" and have Jetty load up right away (no creating of a web-app directory or packaging of a war or anything like that).
> What I hate about ant based projects is that each ant file is yet another build script to figure out. That and dealing with .jar's of course.
Most of the users do not need to worry about the build xml as long as
they know which target to run.
>
> Yeah, maven can be annoying at times.
>
> ~ David Smiley
> ________________________________________
> From: manuel aldana [aldana@gmx.de]
> Sent: Monday, June 29, 2009 5:36 PM
> To: solr-user@lucene.apache.org
> Subject: Re: plans for switching to maven2 (after 1.4 release)?
>
> I know migrating to maven2 has its pain points but in my view is worth
> it if one sees it as a long run investment. It follows
> standards/conventions and importing projects to IDEs like eclipse or
> IntelliJ is much more straightforward. When using maven getting used to
> a new project using it is also much quicker as grasping propriertary
> builds reinventing the wheel.
>
> After having used maven2 for three years now I really couldn't live with
> it (though in the beginning when migrating builds I was swearing at its
> evil details). Support (documentation + mailing-list) has also greatly
> improved since then.
>
> Because smooth migration is not that easy, one should maybe take the cut
> after release 1.4 or 1.5? Though I am not so much into codebase history
> would like to help out.
>
>
> Grant Ingersoll schrieb:
>> 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.
>>>
>>
>
>
> --
> manuel aldana
> aldana@gmx.de
> software-engineering blog: http://www.aldana-online.de
--
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com
RE: plans for switching to maven2 (after 1.4 release)?
Posted by "Smiley, David W." <ds...@mitre.org>.
FWIW
I strongly agree with your sentiments, Manual.
One of the neat maven features that isn't well known is just being able to do "mvn jetty:run" and have Jetty load up right away (no creating of a web-app directory or packaging of a war or anything like that).
What I hate about ant based projects is that each ant file is yet another build script to figure out. That and dealing with .jar's of course.
Yeah, maven can be annoying at times.
~ David Smiley
________________________________________
From: manuel aldana [aldana@gmx.de]
Sent: Monday, June 29, 2009 5:36 PM
To: solr-user@lucene.apache.org
Subject: Re: plans for switching to maven2 (after 1.4 release)?
I know migrating to maven2 has its pain points but in my view is worth
it if one sees it as a long run investment. It follows
standards/conventions and importing projects to IDEs like eclipse or
IntelliJ is much more straightforward. When using maven getting used to
a new project using it is also much quicker as grasping propriertary
builds reinventing the wheel.
After having used maven2 for three years now I really couldn't live with
it (though in the beginning when migrating builds I was swearing at its
evil details). Support (documentation + mailing-list) has also greatly
improved since then.
Because smooth migration is not that easy, one should maybe take the cut
after release 1.4 or 1.5? Though I am not so much into codebase history
would like to help out.
Grant Ingersoll schrieb:
> 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.
>>
>
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
Re: plans for switching to maven2 (after 1.4 release)?
Posted by manuel aldana <al...@gmx.de>.
I know migrating to maven2 has its pain points but in my view is worth
it if one sees it as a long run investment. It follows
standards/conventions and importing projects to IDEs like eclipse or
IntelliJ is much more straightforward. When using maven getting used to
a new project using it is also much quicker as grasping propriertary
builds reinventing the wheel.
After having used maven2 for three years now I really couldn't live with
it (though in the beginning when migrating builds I was swearing at its
evil details). Support (documentation + mailing-list) has also greatly
improved since then.
Because smooth migration is not that easy, one should maybe take the cut
after release 1.4 or 1.5? Though I am not so much into codebase history
would like to help out.
Grant Ingersoll schrieb:
> 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.
>>
>
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
Re: plans for switching to maven2 (after 1.4 release)?
Posted by Grant Ingersoll <gs...@apache.org>.
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.
>