Open sergeykad opened 8 months ago
Thank you for an issue.
There was an issue #788 for exactly that.
Patch wasn't successful though for Java >= 11. I'll be glad if you have a proper solution.
With the latest Java LTS being 21 I am guessing most of the projects are on Java 11+ by now.
Unfortunately, I do not have experience in Kotlin or writing Gradle plugins, so I probably will not be able to help much. Maybe it's just adding the @Optional annotation as mentioned in the documentation?
Kotlin is quite similar to Java even syntax is not the same. Don't worry about imperfect styling
Optional is not the case as information in the configuration is mandatory.
So it's important to find which variable has not been fulfilled for Gradle.
There's a disabled test which you can use and add an additional argument to pass a debug argument. In GradleVersions.kt there's listed all gradle versions to be tested, almost all of them can be disabled by commenting out or an environment variable to be passed.
Could you please help me?
Links to files mentioned
Hi @sergeykad, I probably fixed the issue. Presumably, configurations must be visible to be cacheable. We'll see how tests will go.
Hi @eirnym, sorry for nagging, but when do you think you will be able to release version 7? The last release was over a year ago.
Thank you for nagging actually. Sorry for keeping you waining.
Hi @eirnym , any news regarding when you will release a new version? This is the only issue that keeps us from using the configuration cache.
Running on Gradle 8.6 with enabled configuration cache results in the following failure: