25 ms·
Gradle has actually saved my build. About 3x faster than my old Maven setup. Also, my build files are much less bloated. The only problem I find is the API upd
by p2detar 5y ago
Gradle has actually saved my build. About 3x faster than my old Maven setup. Also, my build files are much less bloated.
The only problem I find is the API updates between major versions. Still, I’m never going back to Maven. Love Gradle.
Building embedded server apps, many sub projects, single Java/Kotlin codebase.
- lenkite 5y agoThe only reason Gradle is faster is because it uses a daemon for build caching and leverage JVM code optimization. Once you apply that same strategy to Maven, it actually tends to beat Gradle in performance too. See Maven Daemon: https://github.com/apache/maven-mvnd https://github.com/apache/maven-mvnd
- ptx 5y agoAnd if you build from inside IntelliJ, I think it already does essentially the same thing (unless you tell it not to) by importing the Maven project into its internal build system and using a compiler daemon: https://www.jetbrains.com/help/idea/delegate-build-and-run-actions-to-maven.html#delegate_to_maven https://www.jetbrains.com/help/idea/delegate-build-and-run-a...
- InsaneOstrich 5y agoGradle also has the ability to skip things it has already done. It won't recompile code that hasn't changed, won't run tests that haven't changed, etc
- p2detar 5y ago> actually tends to beat Gradle in performance too. Mvnd seems somewhat recent compared to Gradle’s daemon feature. Are there any measurements that confirm this statement? I don’t find any in the repo?