-
Notifications
You must be signed in to change notification settings - Fork 97
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
Error with gradle-build-action v2.11.0 and Gradle 1.12: unable to resolve class PluginManager #1007
Comments
Thanks for the report. I'm quite amazed that Due to the magic of dynamic Groovy, I think simply changing:
to
might be enough to avoid failure on Gradle 1.12. The init script should then load correctly, and the code won't be executed unless you are explicitly enabling Gradle Enterprise injection (which I presume you're not). |
@remkop I've pushed a simple attempt at a fix and it would be great if you could verify that it works. |
@bigdaz That works, thank you! |
The fix has been released in |
Amazingly fast turnaround! Many thanks! |
Summary
Error with gradle-build-action 2.11.0 and Gradle 1.12:
Description
My project picocli supports Java 5 and later.
(GitHub Actions only supports Java 6+, so my CI pipeline tests Java 6+)
After upgrading
gradle-build-action
from 2.8.0 to 2.11.0, I experience the following error:Not sure why this is happening. Does this need to be a fully qualified class
org.gradle.api.plugins.PluginManager
? This class was introduced in Gradle 2.3, so I would not expect this error with Gradle 1.12...Attempted Workaround
I tried to configure as follows with property
gradle-enterprise.injection-enabled=false
but the error still occurs:Log Details
Some more context:
The text was updated successfully, but these errors were encountered: