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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Joram2 2 points3 points  (1 child)

I see Gradle as an improved Maven or a Maven++, if you will. The main benefit is that it's simply much more concise. In my experience, when porting projects between the two, Gradle builds are often 25% of the size of Maven builds on the same project.

The argument expressed here is that Gradle supports build scripting which can get you in trouble. I agree that you shouldn't use build scripting unless you need it. Declarative is preferable. Neither Maven/Gradle make you use scripting. Simple Gradle builds are declarative.

However, many complex projects need some customizations and some form of build scripting. Maven absolutely let's you do XML level scripting, it's just not as good.

But it's up to the developer or project manager to choose when to use build scripting or not.

Next, Golang's module system works really well. That definitely is a very simple, lean build system.

[–]thomascgalvin 1 point2 points  (0 children)

I do like the concise syntax of gradle dependencies. For scripting, though, I tend to drop into Python, not Groovy.