-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
BREAKING CHANGE: Gradle Java Toolchains support for JavaExec and WorkerAPI #526
Conversation
dd44e0f
to
89e8626
Compare
89e8626
to
32f780b
Compare
LGTM except for the latest commit message not being a semantic versioning tag |
32f780b
to
2112597
Compare
2112597
to
4173f41
Compare
Updated the commits and intentio nbehind the change 👍 |
close #526 BREAKING CHANGE: Gradle v5 and v6 are now not supported
🎉 This issue has been resolved in version 5.0.0-beta.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
I've merged these changes to the |
🎉 This issue has been resolved in version 5.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
With the introduction of Toolchains for JVM Projects, there might be some folks that would like to leverage such feature when executing spotbugs either via worker api / javaexec / hybrid.
This pull request adds support for it. For now, this requires explicit opt-in via
If necessary, this could be default in the future but it seems like a safer approach to roll out this feature.
It will be interesting to keep an eye on gradle/gradle#16791
This is a breaking change as Toolchain support was introduced in Gradle 6.7 and became mature in 7.x
I suspect this should be rolled out as maybe 7.+ only? thoughts?