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:Jason Dillon (jaso@gmail.com)
Date:Oct 7, 2008 12:35:44 am
List:org.codehaus.groovy.dev

On Oct 7, 2008, at 1:54 PM, Russel Winder wrote:

Of course the Ant build is a disguised Maven build so perhaps those who favour Maven over Ant or Gradle could take a look at the current POM and make sure an actual Maven build is possible (*).

Of course its possible ;-)

This will raise an issue though -- the GMaven compiler does different things to the "standard" Groovyc joint compiler regarding stub creation for dealing with mixed Java/Groovy projects. Perhaps this needs to be split off as a new issue.

Well, that would be a complelling reason to finally get GMaven and Groovyc using the same backend. If you recall the Maven2 build I implemented before was using the groovyc ant task to handle compilation, which is always an option, just not as powerful (yet supports more language bits).

And also, I haven't heard yet good technical arguments in favour of the switch, nor a real list of active complaints about the current build -- I personnally don't have complaints about our current build, although we could enhance / extend it a bit towards easier release processes.

An awful lot of code gets slipped into Groovy without good technical argument. Be careful about using differing standards.

Right, that is true... and a modular build (any system) could help with that problem some by having new code dropped into sandbox modules, then promoted out when there are actually good technical arguments, backed up by good tests, documented, etc.

I agree that a step as big as a change of build infrastructure needs to be done with care and attention to detail. However the current Ant build is in a very analogous state to the old Maven 1 build. It is growing anarchically and at the very least needs a severe refactoring.

Ant, like Maven 1 (and really kinda all Ant-ish builds) generally tend to end up in this state. The same could be said for some Maven 2 projects, but the general nature of Maven 2 being much more strict on how one configures things, tends to avoid this level of atrophy.

If a sever refactoring is in order then a review is in order. The outcomes are:

1. Refactor the Ant build and continue with it. 2. Switch to a full-on Maven build. 3. Switch to a Gradle build.

3 is of course a magic number.

1 is the loneliest number, 2's company and 3's a crowd.

:-P

--jason