<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 20, 2011, at 5:11 AM, Joern Huxhorn wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><br>Other big projects, like Hibernate and Spring, have also chosen to take the Gradle path. I'm pretty sure that Gradle is "the next big thing"...<br></div></blockquote><br></div><div>I very much doubt it. The big selling point for Maven is consistency - when you move from organization a to organization b (or even from project to project within a company) the same plugins still work the same way. From what I saw Gradle is a lot looser (which many might view as a good thing) so it is easier to customize, but it also means a lot of the standardization is lost. I know that within my own organization that is one of the huge selling points for our configuration management team. It doesn't matter what project they are getting a build from, they can run the same goals and get similar results. If Gradle gets to that same place then it might be just as acceptable, but then it will have lost the main feature you are saying is an advantage. <br><br>Ralph</div></body></html>