News for hackers. Stuff that matters.
Re:Gradle 7.0 by this_user on Sunday April 11, 2021 @03:05PM (#26772601)
Gradle has unfortunately gone the way of Maven in terms of becoming more and more of an unnecessarily complicated time sink.
Re:Gradle 7.0 by bitcharmer on Sunday April 11, 2021 @03:19PM (#26772695)
I have the exact opposite experience. Been on tens if not 100+ Java projects over the last 20 years and 99% of developers I worked with moved away from Gradle after migrating to it from Maven. It's just harder to work with. Maven is super low-maintenance in comparison (and just works).
Re:Gradle 7.0 by isbvhodnvemrwvn on Sunday April 11, 2021 @03:40PM (#26772839)
And Maven makes writing custom build logic just hard enough to discourage people from doing so, which is a very good thing, from my experience of having worked with Gradle for 5 years or so.
Re:Gradle 7.0 by pjmlp on Monday April 12, 2021 @03:08AM (#26776724)
The irony about Gradle is that it is Ant all over again, and on top of that slow as a dog, unless oen allocates several GB for a background daemon.
Re:Gradle 7.0 by oblio on Monday April 12, 2021 @02:36PM (#26783271)
At this point Ant + Ivy is probably better :-D
Re:Gradle 7.0 by pjmlp on Tuesday April 13, 2021 @02:19AM (#26788694)
Actually for anyone without XML allergy it definitly is.

You get IDE completion, script debugging support, it is fast and best of all, it doesn't change in every release.

Re:Gradle 7.0 by this_user on Monday April 12, 2021 @12:14PM (#26781159)
Maybe that is the case if you are working on a project that is large enough to have a dedicated build engineer who stays on top of the Maven situation. But in my experience Maven has been an absolute nightmare to work with for me and others on the teams that I have been on. I don't know how many days have been lost to trying Maven to do one simple thing correctly. And I can tell you that more than once was I eventually so fed up that resorted to using the Ant plugin. That was usually able to solve a problem in five minutes that I had already spent a day on trying to get Maven to cooperate.

That being said, when I switched over to Gradle almost ten years ago, it was still only a marginal improvement, but an improvement nonetheless. Unfortunately, things only seem to have gone downhill from there.

Re:Gradle 7.0 by bitcharmer on Monday April 12, 2021 @05:02PM (#26785136)
You represent the 1% of java developers who think Gradle is better than Maven. And that's OK because as with everything else there is an element of personal preference to everything.

But that doesn't change the fact that overwhelming majority of professional java devs avoid Gradle like the plague.

And no, we don't have a dedicated maven guy in every project. Maven is just too simple and well understood for that.

Re:Gradle 7.0 by jhhh on Sunday April 11, 2021 @03:27PM (#26772765)
To support java 16 all I had to do was change the release tag in my compiler plugin and everything just worked. Didn't have to ugprade maven, didn't have to upgrade the compiler plugin. Gradle users had to wait until they released another entire major version with all the churn that entails.
Re:Gradle 7.0 by snafu109 on Monday April 12, 2021 @01:54AM (#26776394)
Gradle has support for running and building with different JDK versions (it's not new with Gradle 7 but it's a recent feature).

So it was possible to support building Java 16 projects while running Gradle on a supported Java version before Gradle 7 was released.

https://docs.gradle.org/current/userguide/toolchains.html

Re:Gradle 7.0 by jhhh on Monday April 12, 2021 @02:16AM (#26776474)
Doesn't really seem like what you are saying is true: https://github.com/gradle/gradle/issues/13481.
Re:Gradle 7.0 by snafu109 on Monday April 12, 2021 @03:40AM (#26776867)
I'm guessing you only read the issue or title on that link, because the second comment on that issue is from one of the Gradle maintainers suggesting using toolchains (which I linked to), with follow ups from various users advising some success, allowing them to target Java 16 while running Gradle on an earlier, supported version.
Re:Gradle 7.0 by jhhh on Monday April 12, 2021 @10:25AM (#26779787)
The last comment by a gradle team member, before closing the ticket says "... you won't be able to run Gradle 6.8.x on Java 16". Some users having some success compiling isn't really a ringing endorsement of a build system when it's clearly not working completely.
Re:Gradle 7.0 by snafu109 on Monday April 12, 2021 @06:51PM (#26786166)
> "... you won't be able to run Gradle 6.8.x on Java 16"

Exactly. But you could run Gradle on Java 8-15 and use the new toolchains support to build with Java 16.

I'm not saying setting up toolchains is frictionless or even reliable yet (given the feature is so new) but it's there.

Re:Gradle 7.0 by levosmetalo on Sunday April 11, 2021 @03:18PM (#26772689)
Sorry, but maven is an order of magnitude better than gradle. In most cases it just works and is blazing fast compared with the alternatives.
Re:Gradle 7.0 by pjmlp on Monday April 12, 2021 @03:09AM (#26776734)
When Gradle advocates tell it is faster than Maven, they usually let it off that Maven doesn't require a backgroud daemon eating away GBs to be fast.
Re:Gradle 7.0 by kaba0 on Monday April 12, 2021 @07:25AM (#26778171)
Why is it a problem exactly?
Re:Gradle 7.0 by pjmlp on Monday April 12, 2021 @08:27AM (#26778604)
> eating away GBs to be fast.
Re:Gradle 7.0 by kaba0 on Monday April 12, 2021 @08:44AM (#26778745)
Make something fast, cheap, stable; choose 2.
Re:Gradle 7.0 by pjmlp on Monday April 12, 2021 @09:24AM (#26779116)
Gradle is none of those three.