(Mind you, I haven’t use Gradle!)
# announcements
m
(Mind you, I haven’t use Gradle!)
n
maven is far from perfect but gradle is not the solution
p
gradle is an abomination
😂 2
👏 1
a
@poohbarbad experiences with gradle?
n
“failure by design”
p
i have no good experiences with gradle.. i think the whole design and the whole approach is contraproductive.. i also think that groovy sucks so that turns me off right away, and i hate what gradle logs
build programming language with no auto-complete? what a grand idea
r
anybody who writes gradle build files with kotlin?
there you would have your auto-completion back I suppose
d
@nfrankel can you elaborate? My experience hasn't been bad at all.
f
am I the only one that's never really had to write code in a Gradle build file?
n
@dnorton gradle was designed to be flexible by default (just like Ant was) in reaction to maven being “too strict” but it makes it very easy to do quick-and-dirty hack at least, in maven, you need to write a plugin and it takes time so that you do it only if it’s necessary with gradle, anyone can write its crap into the build just because he thinks he knows better this was my thinking before and i witnessed it first hand
oh, yes and as an integration testing aficionado there’s no integration testing phase in gradle but as gradle fanboys will tell you: “you can easily add it” back to ant again...
p
i have never had to write a plugin for maven
but i will soon have to if the general trend continues with abandoning the only sane java build tool and going into the insanity of gradle
n
🤗
i feel you
d
@nfrankel thanks for the explanation. I've really only used Gradle on smaller projects that don't have complex build requirements. I did, however, roll my own integration test task. So, I get your point. It's a matter of structure/governance for you. IMO, those issues are why interest in Gradle has flattened over the last year.
n
i let everyone draw his own conclusion for me, it’s pretty clear 🙂