I really feel that gradle is always getting in my ...
# random
b
I really feel that gradle is always getting in my way…
😩 1
w
For example what? 🙂
b
Yesterday intelliJ crashed in the middle of a project update. And gradle was complaining about some file it couldn't treat. (I had to kill all the daemons, kill the cache and then it worked)
But in general, I find its syntax to be really confusing and every tutorial/documentation/project I see have completely different syntax or approaches to do the same thing
w
I find its syntax to be really confusing
That’s just Groovy, and it is a bit different from Java/Kotlin, but is it that confusing?
completely different syntax or approaches to do the same thing
That’s one of the strengths of Gradle, but I see what you mean. Anyway things like Daemon, cacheability or any issues deep in Gradle I agree are tough. Just for me are pretty rare
b
I'm using the gradle kts
what is confusing is how dependencies are handled, and the fact that it looks like kotlin, but some things like plugins can't see variable from outer scope so you define versions twice… I'm always struggling to handle dependencies of subprojects
l
Ah… dependencies versions, it's a true pain point in mutli-modules projects, which are gaining a lot of momentum. @jmfayard and I are working a solution for that in the #CP5659EL9 plugin.
d
A lot of the dependency management features we helped with are also starting to land - native alignment, constraints, platforms, BOMs, etc - all features that can help there too
l
@danny What is native alignment?
d
It's https://docs.gradle.org/5.0/userguide/managing_transitive_dependencies.html#sec:version_alignment, I'm in the habit of calling it native because we have an implementation of alignment in our resolution-rules plugin. More accurate to say built-in I guess