On Wed, 2011-03-09 at 10:02 -0800, Cédric Beust ♔ wrote: > Agreed. > > > I think that today, Gradle is what comes the closest to what I think > would be the best compromises for a build tool: > 1. The language should be mostly declarative, because build files > are typically declarative for the most part. > 2. It should be possible to write code whenever necessary. And if > you want to take a subset of a fully blown language, I think > the necessary features are 1) declaring variables that can be > visible by subtasks, 2) expressions and loops and 3) > inheritance, overriding and specialization. > 3. Compatible with Maven repositories. > 4. Easy tooling so that writing build files can be done entirely > in your IDE (completion). > Gradle definitely looks very promising and as far as I can tell, it > has 1, 2 and 3 covered. 4 is still not there and I find it sometimes > hard to figure out what I need to put in my build files, which ones > are the keywords and which ones are the targets. But there is > certainly nothing preventing it from getting there, it will just take > a bit more time (and hoping that Hans and co are aware of the > importance of this particular item).
The GrEclipse folk are working on better integration of Gradle into the Eclipse/Groovy set up. When they release 4 should begin to be covered in Eclipse. I believe IntelliJ IDEA already has some support for Gradle files. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
