I just did a quick tally based on where it seems people's overall preference was (some people didn't actually +1 any choice, but rather +0'd one and -0'd the other -- so I took the +0 as their preferred option) and it looks like Maven is clearly the winner. Here is what I came up with:
===== Maven ===== Ate, Niels, Okke, Suresh, Marlon, Sander, Raminder, Woonsan, Jasha, Ard, Unico ======= Ant/Ivy ======= Jesse, Ross, Matt, Tony, Scott ======= Gradle ======= Sylvain -- As I understand it Maven has a very rigid project structure -- so if that's indeed the case (meaning there is really nothing we need to discuss as a group about how we structure things) then would it make sense to have one of the Maven experts in the group volunteer to go ahead and get the Maven based project all setup for us? --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
