Hola, Like a couple of other people, I wasn't a big fan of Maven 1, so always voted against it as the canonical build system, especially since Ant is still much more widely supported. However, I think Maven 2 brings great improvements, so I don't mind us at least trying it out to see how it works.
FWIW, Maven 1 had a way (a plugin in maven terminology) to generate a pure Ant build.xml file from a Maven POM. I'm sure Maven 2 still has this capability, which would obviously reduce our maintenance burden. Yoav On 5/30/06, Darren Vengroff <[EMAIL PROTECTED]> wrote:
I think your side-by-side proposal is a good one. Let me polish the pom a little and then I'll submit it. This will happen the first time I get a free moment in the next few days. -D -----Original Message----- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:35 PM To: [email protected] Subject: RE: Ant, Javadoc, and JUnit : I hope it's not too off topic, but since you are hacking away at the build, : I'll ask. Have you thought of moving from Ant to Maven2? I'm new to solr, : so if it's been hashed over and rejected for valid reasons, excuse my : intrusion. have i personally thought about it? no. has anyone else thought about it? i don't know. has it ever come up in discussion on the mailing lists? no. I don't know about any one else, but I don't have any particular affinity for ant other then: it's what i know, it works fairly well, and it's fairly common so using it in the project doesn't create any immediate hurdle for new developers wanting to build solr. If maven(2) is better then ant in these respects, then i'd be happy to switch, but it doesn't quite seem like there's any serious motivation to do so -- particularly on that last point, maven isn't quite as common as ant is it? (let alone maven2). I get the "early adopter" chicken and egg problem for tools, but at ths point Solr is still in the "trying to get noticed" phase and supporting the least common denomiator is probably a good idea. : FWIW, I just put together a quick Maven2 pom.xml file for Solr and it seems : to work well. It's probably not be practical for general use until Lucene : itself uses Maven2, but I'd be happy to contribute it if and when that : happens. Definitely! ... if you'd like to contribute it now, it could probably live side by side with the build.xml so people comfortable with maven could use it instead if if they prefer ... right? (or is my vast lack of understanding about maven showing through here?) -Hoss
-- Yoav Shapira Nimalex LLC 1 Mifflin Place, Suite 310 Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com
