4 ms·
For java, I would look at gradle, not maven. Of course, gradle hooks into the whole maven ecosystem but that is one of its advantages. Everybody in Java land u
by bhaak 9y ago
For java, I would look at gradle, not maven.
Of course, gradle hooks into the whole maven ecosystem but that is one of its advantages. Everybody in Java land understands Maven packages but how you generate doesn't matter.
- pjmlp 9y agoAndroid builds have renewed by love for Maven. If it wasn't for Android, I wouldn't bother 1 second to learn Gradle. But I guess Groovy needs some project to keep it alive, now that no one remebers the days JSF beans would be written in Groovy or JUGs were holding Grails talks month after month.
- kuschku 9y agoDon’t worry, Gradle is moving to kotlin for build scripts already. Groovy will soon be a (failed) thing of the past.
- vorg 9y agoSeems like every other site is converting its Gradle builds into Bazel.
- nvarsj 9y agoGradle degraded the dependency experience significantly from maven. Maven had a deterministic, sensible (and selectable) way of dealing with conflicts - gradle just defaults to "largest version wins". Similarly, gradle chucked the whole idea of being able to manage common sets of dependencies across multiple projects easily (the maven super pom). I mean, it's all programmable in gradle, but it pretty much ignored the excellent work maven had done except to use its repos.