Hey Ewan, No worries. I'm familiar with Maven, but I'm more than happy to put some effort into Gradle. It looks like a good choice. I did a few quick checks, Jenkins supports Gradle with a plugin, Elipse support Gradle with a plugin and that's for me the important part.
Still willing to give it a go :-) If anybody with a bit of gradle experience can kick off with a highlevel design of what the build should look like I'll start working on the details. (Or I'll dive into gradle and figure it out any way :) ) Cheers, Hugo -----Original Message----- From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com] Sent: Friday, August 10, 2012 12:59 AM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Binaries (jars) in our source tree/source releases. > -----Original Message----- > From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com] > Sent: Thursday, August 09, 2012 3:57 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: [DISCUSS] Binaries (jars) in our source tree/source > releases. > > > -----Original Message----- > > From: David Nalley [mailto:da...@gnsa.us] > > > > [Snip] > > > > The thread started because the current system isn't really a system, > > it's just a folder full of binary jars which we were advised against > > (and saw another incubator project taken to task by the IPMC). As I > > said elsewhere, I am not opposed to do something else (Maven, Ivy, > > Gradle, $somethingelse), but who is going to pick it up, get it > > running, and educate the rest of us between now and a 4.0 release? > The > > proposed intermediate solution is admittedly inelegant, ugly and > > little better than a shell script, but I doubt there is anyone here > > who doesn't understand it, and it keeps the build system that does > > at least build. > > > > I personally wouldn't mind picking this up after 4.0 (and learning > > something new in the process), but just have no cycles at the moment > > to do so. I am happy for someone else to do it, we just haven't had > > anyone jumping to own the task. > > Yes, I've noticed the lack of people stepping forward ;-) > > If it comes down to it, then I will do it. That's going to take me > away from other release-related tasks, but Chip and John and you seem > to have most of that under control anyway, so we can probably afford > it. > > If I'm the one who does it, then I'm going to use Gradle unless > someone tells me otherwise. I have been reading around, and the > frustrations that I've had with Maven in the past are precisely the > ones that Gradle was designed to address, and I think that it's a good > choice for us. I am open to other people throwing their $0.02 into > that discussion, but they'll have to do it soon! And now that I read the rest of the thread, I should apologize to Hugo, who did offer some time if we went with Maven. What do you think, Hugo? Feel like trying Gradle? Prefer to stay with Maven? Ewan.
