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, Gradle felt
like a toy (I must be wrong since the Hibernate guys are serious).
- a Maven 3 (the lead, Jason) presentation: he basically went over all
the things I hate about maven 2 and stated that maven 3 or 3.1 would fix
them while remaining backward compatible. He showed a large
multi-project build with tons of sources files and it was relatively fast.
It will be very interesting to see how hibernate's experimentation with
Gradle goes and how the maven guys react.
Nevertheless, I am convinced that most of the problems in our build are
fixable, by cleaning up our build:
If I get some time for that, I 'd love to pull the effort to fix those
With kind regards,
Geoffrey De Smet
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> wrote:
> Before you move to Maven 3. There is still a chance to do the right thing:
> one of the JBoss projects ( Hibernate ) already realized that. Time for
> 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 mailing list