DEV Community

Discussion on: JVM devs who prefer Maven over Gradle, what are your reasons?

Collapse
 
cauchypeano profile image
Igor Konoplyanko

I would personally prefer Gradle over Maven for following reasons:

  • Performance - gradle supports parallel builds this making possible to get fast build times. Maven sucks at this (maybe till version 2, don't know current state)
  • Readability: yes, it's more readable than tons of xml's
  • Reusability: it's much easier to write plugins and extract parts of your build in separate files.
Collapse
 
skapral profile image
Kapralov Sergey

Personally, I like the idea of gradle, but don't like groovy. For me, groovy is counterreadable. If only there was a way to do the same with plain Java...

Collapse
 
ondrazizka profile image
Ondrej Zizka • Edited

Hmm. Many years old version sucks. Ok then maybe let's compare Gradle 1.x with Maven 2?

And regarding "it's much easier to write plugins and extract parts of your build in separate files."
That is exactly the reason why I would not choose Gradle - because of the inventions that the developers bring into the build. Instead of describing the project, Gradle falls back to command the tools what to do, without any value added. Maven has managed to build a build culture which leads to actually readable builds - not in terms of concise, but highly standardized and quickly understandable - compared to Gradle spaghetti code.