Skip to content
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

fix: use internal property to avoid issues with configuration cache #857

Merged
merged 3 commits into from
Mar 22, 2023

Conversation

C-Otto
Copy link
Contributor

@C-Otto C-Otto commented Feb 27, 2023

fixes #670

@hazendaz
Copy link
Member

LGTM, asked @KengoTODA to check as not familiar enough with gradle but looks fine and builds pass.

@C-Otto
Copy link
Contributor Author

C-Otto commented Mar 20, 2023

FYI, Gradle 8.1 promotes the configuration cache to "stable": https://docs.gradle.org/8.1-rc-1/release-notes.html#promoted-features

@martijndwars
Copy link

Would love to see this land in the Spotbugs plugin -- it's currently the only plugin in our build that breaks configuration cache.

Copy link
Member

@KengoTODA KengoTODA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for proposing this fix!

@KengoTODA KengoTODA changed the title use internal property to avoid issues with configuration cache fix: use internal property to avoid issues with configuration cache Mar 22, 2023
@KengoTODA KengoTODA merged commit d068aa2 into spotbugs:master Mar 22, 2023
@github-actions
Copy link

🎉 This PR is included in version 5.0.14 🎉

The release is available on:

Your semantic-release bot 📦🚀

@C-Otto C-Otto deleted the configuration-cache branch March 22, 2023 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configuration Cache: invocation of Task.project at execution time is unsupported.
4 participants