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
Auto-provisioning/auto-detection of IBM Semeru toolchains is broken with Gradle 7.6 #23053
Comments
@jbartok could you please provide clarity on your previous statement? I don't quite understand where you/Gradle are getting Thanks, Edit: I see now from the fix. Thanks. |
…eru runtimes (backport) Fixes #23053 It doesn't make sense to have both the IBM and IBM_SEMERU vendor values. Co-authored-by: József Bartók <jbartok@gradle.com>
I assume this means that one of the next nightly builds could be used for verifying your changes? |
Yes, https://gradle.org/release-nightly/ should contain the fix (but this is a nightly for the upcoming 8.0 version). |
I changed my build setup to use jdk-11.0.17+8 and then pointed to gradle-8.0-20221216001954:
So, that part is working. |
Expected Behavior
Build works with gradle 7.5.1 and jdks are auto provisioned as declared in build.gradle:
Current Behavior
Upgrading to gradle 7.6 the build now fails with:
Context
Auto-detection/auto-provisioning of Gradle toolchains is broken with gradle 7.6
Steps to Reproduce
Your Environment
Detected toolchains:
The text was updated successfully, but these errors were encountered: