On 11/07/2010 23:55, Michael Neale wrote:
I think you mean gradle - but yes, that makes sense.
There were others I was fond of - buildr was one - as far as I know,
the nice things about all these "alternative" tools is that they at
the least reuse the maven repositories and meta data - so it isn't
starting from scratch.
As a consumer of libraries, I like having declarative dependencies, no
matter what my build system is, so that is a good thing.
I think the drools build is pretty much as complex as hibernate - more
so even - drools has a few stand alone components that have quite
fiddly build steps (which still probably aren't fully automated),
things like GWT, building cut down app servers etc... so it is worth
watching closely how hibernate do.
Myself - I know that MarkP has struggled for years with maven, and won
most battles - so the day I see mark switch to gradle/whatever, is the
day I would probably switch.
Build systems can suck time like nothing else,
I've wasted so much time
in the past. So in general the less time I spend working on the build
the better, and at the moment it's not taking up a lot of time, so I
have to get a strong itch to swap one pain for another ;)
We will be splitting up the build going forward, so we'll see how much
pain we go through there and whether it creates a strong enough itch.
Maven 3 promises to be compatible - so that is an improvement over
maven1 (not sure if many remember that... oh the horror).
On Mon, Jul 12, 2010 at 8:23 AM, Mark Proctor <mproctor(a)codehaus.org
I'm happy to let the hibernate people guinee pig Grails. Initially
we'll move to maven 3 (as it's backwards compatible), and for the
maven is still what most people are familiar with.
We'll be restructuring the build over time and if maven 3 doesn't do
what we need and/or hibernate people are reporting amazing results
no sign of improvements to maven, then we can evaluate Grails.
On 11/07/2010 14:55, Geoffrey De Smet wrote:
> Steve makes some good, valid points on that blog about Maven 2.
> I get the feeling that Maven 3 fixes a lot of those problems and the
> maven 3.1 promises a lot too.
> At Devoxx 2009 I saw 2 presentations:
> - Gradle (the lead, forgot his name): showed a build of a one module
> project with one source file - and it was fast. All in all,
> like a toy (I must be wrong since the Hibernate guys are serious).
> - a Maven 3 (the lead, Jason) presentation: he basically went
> the things I hate about maven 2 and stated that maven 3 or 3.1
> them while remaining backward compatible. He showed a large
> multi-project build with tons of sources files and it was
> It will be very interesting to see how hibernate's
> Gradle goes and how the maven guys react.
> Nevertheless, I am convinced that most of the problems in our
> fixable, by cleaning up our build:
> If I get some time for that, I 'd love to pull the effort to fix
> With kind regards,
> Geoffrey De Smet
> Salaboy schreef:
>> I think that after the release it would be nice to research on
this kind of things. And now if jboss has another framework that
uses gradle, probably will be easier to migrate
>> - CTO @ http://www.plugtree.com
>> - MyJourney @ http://salaboy.wordpress.com
>> - Co-Founder @ http://www.jbug.com.ar
>> - Mauricio "Salaboy" Salatino -
>> On Jul 9, 2010, at 4:25, tolitius<webakaunt(a)gmail.com
>>> Before you move to Maven 3. There is still a chance to do the
>>> one of the JBoss projects ( Hibernate ) already realized that.
>>> Drools to do to.
>>> View this message in context:
>>> Sent from the Drools - Dev mailing list archive at Nabble.com
>>> rules-dev mailing list
>>> rules-dev(a)lists.jboss.org <mailto:email@example.com>
>> rules-dev mailing list
>> rules-dev(a)lists.jboss.org <mailto:firstname.lastname@example.org>
> rules-dev mailing list
> rules-dev(a)lists.jboss.org <mailto:email@example.com>
rules-dev mailing list
Michael D Neale
rules-dev mailing list