Why Gradle Is DESTROYING Maven

In the Maven vs. Gradle build wars there's still everything to play for, but how did we get here? Join this journey of discovery from Maven's humble beginnings as an Ant-killer in 2001, to 2008 when Gradle dared to challenge the build tool status quo, to the present day where Gradle usage amongst JVM developers continues to grow.

✔️Gradle's humble beginnings 0:00
✔️Back to when Apache Maven was born 1:33
✔️Maven makes inroads against Apache Ant 3:44
✔️Hans Dockter's dream of a better build tool 4:17
✔️Gradle's winning streak 5:46
✔️Maven vs. Gradle in 2021 6:55
✔️What holds back projects from migrating to Gradle 7:29
✔️What next? 9:29

[wisestein]

I watched enough of these “grade vs maven” vids but all were annoyingly missing something that helped to understand it. Couldn’t put my finger on what though.
You sir, nailed it with this video. I needed the story. Thanks!

[martinschrodt]

I hated gradle for a long time, because I was thinking that making it so powerful by allowing code itself to be in the build script would inevitably lead to IDEs not understanding the build process anymore. It was like ANT in disguise. I just recently looked at it again, and understood that a) IDE integration has really improved, and b) it is on you to keep the build script close to the standard, but sometimes there's just no way to do things with maven that are easy in gradle by just adding a tiny bit of code. Especially when projects get bigger, and there's stuff like company wide dependency management and CI, maven becomes a mess. So I think the time is right to switch to it.

[gamersinger]

Hello Tom. It was a very informative video.
Maven <3

[shreem]

Thanks for going to depths of the origins of Gradle...

[kirillkir]

How do you implement something like this in a few minutes in gradle?

mvn versions:use-dep-version -DdepVersion=$DEP_VERSION

Gradle more looks like a hipe tool from JS world

Maven has simple and strict structure in other hand you have gradle spaghetti where anyone write as he want and it is really hard to automatize and understand

[TheNeoxpert]

Maven is better. Because you don't need a complex compiler to parse the build description. Which is just XML, so you can pretty fast implement your own maven.

Another problem with Gradle: you can have overcomplicated build scripts.

[Talaria.School]

From the cradle to the grave #tupac.
~./gradlew

[ventin]

Maven has pom.xml. What is gradle's equivalent?

[stefanhirche]

It is still not really possible to build rcp projects with gradle, you have to use tycho on maven. It's really a pain as it is slow and cumbersome in contrast to our gradle builds.

[feoktant]

This video disinform the audience - Maven pom file could be written in any format, yaml, json, or even Java, Scala or Kotlin

[EricKolotyluk]

Yes, it is very apparent that you love Gradle, but the does not make Gradle better than Maven. There are still many characteristics of Maven that will always be better than Gradle. For example, quality. Gradle documentation and diagnostics are terrible. Granted your videos on Gradle are very high quality, but wrt Gradle, this is the exception and not the rule.