-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable stable config cache #1588
Conversation
90b9600
to
585a21b
Compare
585a21b
to
32a5317
Compare
https://github.com/diffplug/spotless/actions/runs/4274264364/jobs/7440768996
https://github.com/diffplug/spotless/actions/runs/4274264364/jobs/7440768895
|
Thanks for the PR, if all these warnings go away we can merge this. But I'm quite disappointed that the config cache has become stable. I think the design is fatally flawed (#987), writing a Gradle plugin has become far more difficult for little benefit. It reminds me quite a bit of the Eclipse ecosystem when Eclipse 4 and "p2" were first proposed. P2 and E4 were ambitious systems that fundamentally could not deliver on what was promised, and the good parts of Eclipse eventually rotted to nothing due to the friction of the unmet and unmeetable promises of its "next-gen" components (e.g. gradle/gradle#13510 is not possible to implement, but plugin authors have to jump through onerous hoops anyway). Gradle doesn't have an imminent competitor the same way that Eclipse did, but the configuration cache serialization requirement is imo a catastrophe for the ecosystem. |
Suppressed all errors on CI. |
Thanks for this, linking to all the issues tracking the configuration cache issues was very helpful. |
https://docs.gradle.org/7.6.1/userguide/configuration_cache.html