69 messages in org.codehaus.groovy.devRe: [groovy-dev] Building Groovy
FromSent OnAttachments
Russel WinderOct 6, 2008 4:36 am 
MingfaiOct 6, 2008 4:47 am 
Hans DockterOct 6, 2008 4:50 am 
Hans DockterOct 6, 2008 4:55 am 
Jochen TheodorouOct 6, 2008 4:56 am 
Guillaume LaforgeOct 6, 2008 7:17 am 
Hans DockterOct 6, 2008 7:51 am 
Russel WinderOct 6, 2008 7:59 am 
Guillaume LaforgeOct 6, 2008 8:19 am 
Guillaume LaforgeOct 6, 2008 8:25 am 
MingfaiOct 6, 2008 8:28 am 
Guillaume LaforgeOct 6, 2008 8:36 am 
Hans DockterOct 6, 2008 1:46 pm 
Guillaume LaforgeOct 6, 2008 1:54 pm 
Hans DockterOct 6, 2008 1:54 pm 
Jochen TheodorouOct 6, 2008 2:03 pm 
Guillaume LaforgeOct 6, 2008 2:09 pm 
Paul DuffyOct 6, 2008 7:06 pm 
Luke DaleyOct 6, 2008 8:47 pm 
Guillaume LaforgeOct 6, 2008 9:44 pm 
Russel WinderOct 6, 2008 11:25 pm 
Russel WinderOct 6, 2008 11:54 pm 
Russel WinderOct 7, 2008 12:03 am 
Jason DillonOct 7, 2008 12:23 am 
Russel WinderOct 7, 2008 12:24 am 
Guillaume LaforgeOct 7, 2008 12:30 am 
Hans DockterOct 7, 2008 12:35 am 
Jason DillonOct 7, 2008 12:35 am 
Hans DockterOct 7, 2008 12:36 am 
Jason DillonOct 7, 2008 12:41 am 
Guillaume LaforgeOct 7, 2008 12:54 am 
Jason DillonOct 7, 2008 1:40 am 
Guillaume LaforgeOct 7, 2008 1:50 am 
Jason DillonOct 7, 2008 1:55 am 
Guillaume LaforgeOct 7, 2008 2:25 am 
Guillaume LaforgeOct 7, 2008 2:35 am 
Jason DillonOct 7, 2008 3:09 am 
Guillaume LaforgeOct 7, 2008 3:12 am 
Russel WinderOct 7, 2008 3:17 am 
Jason DillonOct 7, 2008 3:24 am 
Paul KingOct 7, 2008 4:04 am 
ma...@dockter.bizOct 7, 2008 4:19 am 
ma...@dockter.bizOct 7, 2008 4:25 am 
Jason DillonOct 7, 2008 4:36 am 
Jason DillonOct 7, 2008 4:39 am 
Jochen TheodorouOct 7, 2008 5:20 am 
Jason DillonOct 7, 2008 8:19 am 
Jochen TheodorouOct 7, 2008 9:51 am 
Jason DillonOct 7, 2008 10:49 am 
Jochen TheodorouOct 7, 2008 12:03 pm 
Hans DockterOct 7, 2008 2:34 pm 
Luke DaleyOct 7, 2008 3:52 pm 
Jason DillonOct 8, 2008 1:28 am 
Jason DillonOct 8, 2008 1:35 am 
Hans DockterOct 8, 2008 3:11 am 
Hans DockterOct 8, 2008 3:49 am 
Hans DockterOct 8, 2008 4:30 am 
Hans DockterOct 8, 2008 4:40 am 
Jason DillonOct 8, 2008 4:52 am 
Jason DillonOct 8, 2008 5:21 am 
Jochen TheodorouOct 8, 2008 6:23 am 
Jochen TheodorouOct 8, 2008 6:47 am 
Jochen TheodorouOct 8, 2008 6:59 am 
Hans DockterOct 8, 2008 8:33 am 
Hans DockterOct 8, 2008 8:43 am 
Paul DuffyOct 9, 2008 8:58 am 
Paul KingOct 9, 2008 1:15 pm 
Danno FerrinOct 9, 2008 1:27 pm 
Paul KingOct 10, 2008 2:31 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [groovy-dev] Building GroovyActions...
From:Russel Winder (russ@concertant.com)
Date:Oct 7, 2008 12:24:27 am
List:org.codehaus.groovy.dev

On Mon, 2008-10-06 at 17:19 +0200, Guillaume Laforge wrote: [ . . . ]

In this case, it helps Gradle more than it helps Groovy, if Groovy is just seen through this as a mere "scripting glue" for build systems.

More of a win for Gradle than for Groovy here, unless we're happy with people just thinking Groovy is for build automation.

Surely it is the case at the moment that Groovy is just the programming language for Grails in exactly the same way that Ruby is the programming language for Ruby on Rails. We all know this is fallacy but the wider world thinks it true.

Ruby has Buildr, Groovy has Gradle.

By having two high profile projects (Grails and Gradle) showing the benefit of Groovy in different spheres of use, it is made clear that Groovy is of wider applicability that one domain.

What I'm kinda waiting for are real strong technical arguments in favour of Gradle.

In the face of zero data this is unlikely to bear fruit. The same happened in the "Great Maven 1 Debate". Nothing happened apart from waffling until I actually put an Ant build together and force people to try it.

I'm pushing you guys to be better at technical marketing here :-)

Not quite, you are acting as a unit of inertia, and that is the correct thing to do as a project manager. Actually I wish you would do this more widely in the Groovy project. For me too much gets slipped into Groovy without debate and without wide agreement. I think we have here a classic example of doing the right thing is some but not enough circumstances.

Returning to the main point: argumentation without data is not going to progress this, there has to be an example build on which to create proper debate and thence choice. Currently we have an Ant build (that needs a good rewrite), a potential Gant build, and a potential Maven build. For the expense of having a build,gradle file in the filestore (even if just temporarily) and giving Hans write permission to the Groovy store, you lose nothing and potentially gain a great deal. As I see it there can be a small competition between the Antofiles, the Mavenistas and the Gradlers to present to the Groovy developers a selection of build systems for their delectation and thence choice.

Where this debate started was that if people put effort into doing new builds (Ant, Maven or Gradle) then it must be a fair playing field with no predetermined decision already made.

Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077