+1 for Maven because of all the available plugins, IDE support and most important the dependency repositories. -0 for Ant/Ivy because Ivy ends up using Maven repositories for the dependencies so why not use Maven directly.
Jasha Joachimsthal [email protected] - [email protected] Hippo Europe • Amsterdam • Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20 522 4466 USA • Boston • 1 Broadway • Cambridge, MA 02142 • +1 877 414 4776 (toll free) www.onehippo.com • www.onehippo.org • [email protected] On 7 April 2011 22:35, Woonsan Ko <[email protected]> wrote: > +1 Maven: I like its conventions and many built-in plugins such as antrun, > rat, jetty, cargo, dependency plugins, etc. > +0 Ant/Ivy: I would learn this if chosen. > > Woonsan > > --- On Thu, 4/7/11, Raminderjeet Singh <[email protected]> wrote: > > > From: Raminderjeet Singh <[email protected]> > > Subject: Re: Bootstrapping Rave code: choice of build engine > > To: [email protected] > > Date: Thursday, April 7, 2011, 4:00 PM > > +1 Maven.. i like the IDE integration > > of maven. WAR application build component is most tested one > > :) > > > > +0 Ant/Ivy i would love to learn if we will end up with > > this > > > > Raminder > > On Apr 7, 2011, at 9:37 AM, Sander van der Waal wrote: > > > > > +1 Maven since that's what I'm most comfortable with > > and find easiest to > > > use. > > > > > > -0 Ant/Ivy I'm always struggling with Ivy integration > > in my IDE and in my > > > experience the maven-antrun-plugin is a good mechanism > > for integrating > > > things 'the Ant way' if Maven isn't up to it. > > > > > > Sander > > > > > > On Thu, Apr 7, 2011 at 2:30 PM, Ciancetta, Jesse E. > > <[email protected]> > > wrote: > > > > > >> +1 Ant/Ivy (as I'm already familiar with Ant and > > like to try to keep things > > >> as simple as possible - and my impression of Ant > > is that it is much simpler > > >> to deal with than Maven) > > >> > > >> +0 Maven (I'd be willing to learn it if that's the > > group's overall > > >> consensus) > > >> > > >> --Jesse > > >> > > >>> -----Original Message----- > > >>> From: Ate Douma [mailto:[email protected]] > > >>> Sent: Thursday, April 07, 2011 4:51 AM > > >>> To: [email protected] > > >>> Subject: Bootstrapping Rave code: choice of > > build engine > > >>> > > >>> As we're about to bootstrap the new Rave code > > base, it would be good to > > >>> decide > > >>> now what build engine we will use. This choice > > will have impact on how > > >>> we > > >>> structure and configure our source tree, > > build, test and integration > > >>> environments. > > >>> > > >>> As a Java based project I think we have three > > options: > > >>> - Ant > > >>> - Ant/Ivy > > >>> - Maven > > >>> > > >>> OSEC is Ant based, OGCE, SURFNet and Shindig > > are Maven based, Wookie > > >>> uses Ant/Ivy. > > >>> > > >>> I have a strong preference to use Maven as I'm > > using that for almost > > >>> every other > > >>> project already and IMO has nowadays the > > strongest (automated) ASF > > >>> infrastructure support. But for those not > > accustomed to Maven this might > > >>> require > > >>> some learning curve to get used to as Maven > > does have specific > > >>> restrictions and > > >>> requirements, not the least concerning > > structure and layout of the > > >>> source tree > > >>> itself. > > >>> > > >>> So I'd like to hear the preference of the > > other developers. > > >>> If Ant or Ant/Ivy turns out to have the > > biggest support, I'm fine with > > >>> that as well. > > >>> > > >>> Ate > > >> > > > > >
