+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
