Obviously it is more verbose. But verbosity is not a quality metric of good code. Actually it often goes against quality and understandability. Even without knowing the constraints of my use case the arguments against “straight-Java” I heard so far are very weak.
Thank you. Yes! Actually it goes even beyond that and is dictated by the build process of a huge legacy project. Why it has to be “straight Java” and why the script workaround-hack is no alternative has many reasons and would fill about a dozen pages of text.
Thank you! I will look into it asap. I don’t mind going spelunking in the bowels of the Gradle code base. Still I always have a bad feeling when I only “hear my own echo” in a cave and don’t know if I am going the optimal route. That’s the annoying part. Many Gradle-ninjas (who probably wrote most of the code) are in this thread and could supply a best use-case mini-project in less time it took so far to discourage me using “straight-Java”
We don’t know if people would use it before we have at least a non-trivial multi-project example in “straight-Java” on Github people can start tinkering with. Most trivial problems I faced with Gradle scripts took hours to solve or not at all and would have taken minutes with proper IDE support and the Java debugger instead of tedious guessing, googeling and stupid println-debugging.
The consensus in most Gradle problem replies you find in the web is that people use it wrong if they want to do something a little more complicated. This can be something as simple as non-trivial copying of resources or executing an application where you have to establish the classpath on your own.
Most huge legacy projects are very very complicated to build and don’t care about the way Gradle does things. Heck, they were often created before Gradle was even born. Yes, if I need to setup a brand new project I just adhere to some rules and have no beef with Gradle.
Please Gadle-makers, set up some Github non-trivial multiproject example that uses all the standard Gradle features to build a project in “straight Java” using something like GradleConnector.connect() etc.
I think you will be very surprised how many people would like to tinker with such an solution. Or does this endanger selling the KotlinDSL?