15 ms·

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 a

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).

isbvhodnvemrwvn 6y ago
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.
- pjmlp 6y ago
  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.
  - oblio 6y ago
    At this point Ant + Ivy is probably better :-D
    - pjmlp 6y ago
      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.
this_user 6y ago
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.
- bitcharmer 6y ago
  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.

isbvhodnvemrwvn 6y ago

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.

pjmlp 6y ago
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.
- oblio 6y ago
  At this point Ant + Ivy is probably better :-D
  - pjmlp 6y ago
    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.

this_user 6y ago

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.

bitcharmer 6y ago
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.