I don't remember noticing a build time difference between Maven and Gradle. The big difference for me was that with Gradle I could code my way to a solution not supported by the framework or third party plugin (in Groovy or Java) much easier than with Maven. I agree with Juergen, Gradle seemed very intuitive to me out of the box. I guess I've always considered a build a program in itself and Gradle seems to fit that mantra nicely.
I thought Juergen had a great start with Gradle, but I actually prefer SpringSource approach to having one build file for all subprojects instead of broken up into seperate build.gradle so I can quickly scan the dependencies https://github.com/SpringSource/spring-framework/blob/master/build.gradle If the team would like to revist Gradle, I would help Juergen support the build files. It would be nice to know what are the pain points in Maven (or previously with Gradle) so that they can be addressed in version 2. Rob -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Maven-hate-was-Re-VOTE-Release-wicket-6-0-0-beta2-tp4649537p4649566.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
