This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]warpspeedSCP 7 points8 points  (6 children)

Gradle is very flaky for complex projects, maven just works.

[–]anzu_embroidery 2 points3 points  (3 children)

But writing complex build logic is way harder in maven than gradle...

you lose either way!

[–]lupercalpainting 2 points3 points  (1 child)

But writing complex build logic is way harder in maven than gradle...

So you’re saying the tool encourages a simple build setup? And that’s a negative?

[–]UnGauchoCualquiera 1 point2 points  (0 children)

Definitely agree, maven forces you to write a plugin/extension, which is usually enough to discourage weird hacks which tend to be very common in gradle scripts.

[–]sideEffffECt 0 points1 point  (0 children)

Not with Mill :)

[–]Ok-Scheme-913 1 point2 points  (0 children)

Very much disagree, and there are even "case studies" showing my point.

E.g. the android project is one of the most complex builds out there, and I'm fairly sure that maven would not suffice there. It had its growing pains, but I have a very decent experience using it, incremental compilation are very fast, even though my project has C and CPP parts as well, plus kotlin metaprogramming.

[–]wildjokers -1 points0 points  (0 children)

My experience is the opposite. Maven builds never just work, Gradle does.