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:Guillaume Laforge (glaf@gmail.com)
Date:Oct 7, 2008 1:50:39 am
List:org.codehaus.groovy.dev

On Tue, Oct 7, 2008 at 9:24 AM, Russel Winder <russ@concertant.com> wrote:

[...] 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.

I'm not too much convinced considering all the people I know and heard of using Groovy without Grails, and all their use cases. This is far from the truth, and I'm not sure how you can say that "the world" thing that, unless you're ubiquituous and omniscient :-) But you may well be ;-)

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.

I don't deny it at all. The more use cases we can show people, the better. But I'm usually not for the sake of change just for the sake of change.

[...] 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.

So, if you think so, just go ahead a create a full Gradle build for Groovy. I'm totally fine with that, and I think it's going to be the best way to see how better Gradle can be for Groovy.

But I expected you had some good arguments without needing such work to be done beforehand. I suspect neither of Hans nor you would have started Gant or Gradle without having good reasons to do so.

[...]

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.

I should certainly be stricter here and there, but I don't want to frighten people and make them flee away and stop contributing altogether. It's hard to find the right dose of strictness / inertia, and the right portion of freedom of innovation. Furthermore contributors and committers have their qualities and defects: some are awesome coders but bad documenters, others are good at everything, some are good at giving vision but fail to think about all corner cases, some don't have so little time to contribute, etc. It's not easy.

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.

Go ahead, and both write a Gradle build and commit it. That's great and we'll be able to judge more easily what's best to do with the current build.

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.

Agreed. So far no decision has be pre-made. It's just that I know the fate of some similar efforts (ie. the Maven 2 build for instance): nobody really took time to properly evaluate it, despite the time spent by Jason to bring it to life. If he had known beforehand, perhaps he'd have better used his time to contribute to other areas of Groovy. That's why I wanted to be convinced before seeing any actual new build, as I expected you had good technical arguments to make your point.

So +1 for contributing a Gradle build.