chore: use Gradle toolchains for JDK provisioning #5989
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It enables automatic JDK provisioning (e.g. download), and it enables using different JDKs for executing Gradle and for building JMeter.
The target bytecode is still 1.8 (it would be nice to bump the minimum requirements to Java 11), however, the build would require JDK 17 (it would automatically download one if none is detected locally)
Java version can be specified when building with
-PjdkVersion=11
You could use
./gradlew -q javaToolchains
to list the detected toolchains.See https://docs.gradle.org/8.0/userguide/toolchains.html#sec:consuming
Fixes #5986