-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
VersionCatalogUpdateTask fails with configuration cache enabled #103
Comments
What is the exact error you are getting? Past issues around this pointed to the dependency versions plugin not being compatible, but that may have changed. I quickly tried to reproduce this using an included build but I got unrelated issues trying that. If you can supply a small project that reproduces that issue it would be very much appreciated 🙏 |
I'll see if I can supply a small sample project, until then here's the error:
I get the same stacktrace with versions 0.44.0-0.46.0 of https://github.com/ben-manes/gradle-versions-plugin |
Thanks, I think most of the |
If you are able to try the While testing I had a few weird moments where it looks like the reports are empty when running the |
I gave it a try and it the task completed successfully the first time it ran but with the following warnings:
Running it a second time resulted in Build failed with the following message:
Edit: Seems to work now, good job! The warnings are still there as you mentioned but the task completes successfully so it's not an issue. |
😬 Thanks for testing! I'll probably release this next week. |
Describe the issue
VersionCatalogUpdateTask
fails when configuration cache is enabled ingradle.properties
when running the task using command./gradlew versionCatalogUpdate
Steps to reproduce
Enable configuration cache in a project by adding the line below in the
gradle.properties
file:org.gradle.unsafe.configuration-cache=true
and run the previously mentioned task. Using Gradle 7.6.Workaround
Add below code in the build.gradle.kts root file:
I hope there will be an update to be able to skip above workaround.
The text was updated successfully, but these errors were encountered: