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 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,
ow which target to run.
>
> Yeah, maven can be annoying at times.
>
> ~ David Smiley
>
> From: manuel aldana [ald...@gmx.de]
> Sent: Monday, June 29, 2009 5:36 PM
> To: solr-user@lucene.apache.org
> Subject: Re: plans for switchi
On Tue, Jun 30, 2009 at 1:48 PM, Fergus McMenemie 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 m
>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 p
: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
I
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 a
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.
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
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
