Open dweiss opened 1 month ago
Thanks for opening this @dweiss ! Indeed I reported slow test startups in IntellJ, but it makes sense that the problem is more widespread and related to gradle getting its ducks in a row
These are related issues because Intellij starts gradle to build its project/ data model, which is then used to create Intellij project.
Description
This has been mentioned by Mike Sokolov, I think. Gradle builds have become sloooow to start as we upgraded from version to version. Interestingly, I've come across this hint:
https://docs.gradle.org/current/userguide/sharing_build_logic_between_subprojects.html#sec:convention_plugins_vs_cross_configuration
which is the exact opposite to what we do. I do have some background in aspect-oriented programming so, to me, this kind of cross-configuration and separation of concerns is a way to clean up the build configuration and separate different parts of it. Well, gradle folks clearly think otherwise.
I have not debugged this intensively but when you run even the smallest task with the
-debug
option, you'll see a lot of this:Something must have changed in how this configuration phase is handled. It used to be super fast, now it's a hog.
Rewriting the build to gradle's official guidelines is a longer journey but we may have to do it one day.
Current workaround: use a daemon to keep the project "alive" in memory. Tweak the daemon's timeout, if you wish:
Version and environment details
No response