My preference is Ant/Ivy (maybe EasyAnt not used that yet). It is much more flexible than Maven (or is that just because I know I well). But...
I do not object to Maven as long as someone else is available to maintain it and use it properly. I can maintain Ant, I need to learn about Maven. So, -0 Maven +0 Ant + Ivy (EasyAnt?) Ross Sent from my mobile device. On 7 Apr 2011, at 09:50, Ate Douma <[email protected]> wrote: > 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
