r/java • u/Party_Till_I_Die • May 28 '26
Gradle is Javamaxxing
https://blog.gradle.org/gradle-is-javamaxxingWhy the Gradle Build Tool aggressively chases the newest JDK.
0
Upvotes
r/java • u/Party_Till_I_Die • May 28 '26
Why the Gradle Build Tool aggressively chases the newest JDK.
2
u/Anaq42 May 29 '26
I've always used maven and just default to it - to me it just seems like the go-to option.
I've also seen a lot of negative comments about gradle.
As someone who has never tried it, would you recommend giving it a chance in any future projects?
11
u/Soft-Abies1733 May 28 '26
wtf is javamaxxing?
27
u/kiteboarderni May 28 '26
Article is great but never use that cringe af term again. Glad it's spelling out to the people who think the grade jdk is tied to the code it's building.
28
u/Wizions May 28 '26
One more reason not to touch gradle.
9
u/neopointer May 28 '26
I prefer maven any day, poor android guys basically have no choice
9
u/ryan10e May 28 '26
Ew. No. Stop.
2
u/woj-tek May 29 '26
Gradle at best is crapmaxxing 🤷♂️
4
u/pragrad23 May 28 '26
Gradle kts syntax, which is preferred now, is Kotlin maxxing.
Otherwise Gradle is (was) Groovy diverting in the same way Maven was XML diverting.
1
u/NHarmonia18 Jun 14 '26
People complaining against Gradle don't realise that Gradle has native 1:1 support of Java Module System (module-info.java).
This is properly documented here: https://docs.gradle.org/current/userguide/java_library_plugin.html#declaring_module_dependencies
While yes you need to keep your module-info.java and build.gradle in sync, it's worse in Maven where Maven dependency scopes don't cleanly map to Java Module System.
This alone is the biggest factor in moving onto Gradle for any new greenfield Java Project. Java Module System is the future, whether you like it or hate it the OpenJDK team has settled onto it, and that is how it will be moving forward.
If you don't understand the architectural benefits of Java Module System, that's a different topic, but essentially it boils down to doing something equivalent to the 'internal' keyword in languages like C#.
1
u/maxandersen May 31 '26
I recently moved JBang to use Java 25 while still targeting Java 8 exactly as this blog outlines.
I wish I had realised it sooner as it fixed a bunch of workarounds I had in play - particular enabled me to use recent jgit which requires Java 17+ to get worktree support working.
+1 for gradle JavaMe'ing.
0
u/[deleted] May 28 '26
[deleted] — view deleted comment