HHH-14315 Upgrade to Gradle 6.7 and use toolchains for per-JDK builds #3626
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.
https://hibernate.atlassian.net/browse/HHH-14315
After this PR, we will need a few change in our CI jobs, and then we will be able to test JDK16 (spoiler alert: it works).
This introduces similar changes to hibernate/hibernate-reactive#429.
By default, nothing changes, except that we now use Gradle 6.7.
When specific options are enabled:
Different configurations are also possible, e.g. run Gradle with JDK11, compile with JDK8 and run the tests with JDK15. But the one above is the most interesting and most likely the one we'll use.
@Sanne I think that, considering you need specific options to enable toolchains, we can safely backport to 5.4?