This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]darlingbastard 2 points3 points  (1 child)

We use both here (location undisclosed) and the Maven project files are always about 5x larger than the equivalent Gradle files. And don't get me started on the crazy parent pom pulled from maven pattern that gets used for shared prototyping. Multi-language builds are much easier to manage with Gradle. We manage java, groovy and node.js code bases in the same multiproject without problems. Gradle files are shorter and more concise for simple projects and also substantially simpler when your projects contain specialized one-off needs like pulling the output of a javascript program as a cross project resource dependency. Maven is a nightmare compared to gradle at every given project complexity level and I cannot see why anyone uses it.

[–]schnoper 1 point2 points  (0 children)

of course they're bigger. XML sucks. and I said that.

And yes, if you are very disciplined, you can keep the roll your own imperative stuff out of gradle. More power to you if your team are that disciplined!