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
Dependency Extraction Fails for Gradle < 6 #5424
Labels
manager:gradle
Gradle package manager
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
Comments
JamieMagee
added
manager:gradle
Gradle package manager
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
labels
Feb 10, 2020
@rarkins I think we have to use different gradle scripts for gradle 5 and 6 |
Or use |
if you know how to 😅 |
🎉 This issue has been resolved in version 19.129.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 19.129.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
manager:gradle
Gradle package manager
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
As reported in #4471:
The new gradle extraction script depends on a type that was introduced with Gradle 6, leading to error like this when it is executed on against a project with a Gradl 5 wrapper:
The text was updated successfully, but these errors were encountered: