(2.5.x) Bump java 19 to 21 #1245
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abelsromero
changed the title
abelsromero
force-pushed
the
bump-java-19-to-21-branch-2.5.x
branch
from
49ecf5c to
feeb19d
Compare
|
Nevermind, there's no Gradle (v7.x or v8.x) compatible with java 8 and java 21. I guess it's "best effort" for java 21 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thank you for opening a pull request and contributing to AsciidoctorJ!
Please take a bit of time giving some details about your pull request:
Kind of change
Description
What is the goal of this pull request?
Ensure v2.5.x is tested on Java 21.
How does it achieve that?
Add Java 21 to CI.
Are there any alternative ways to implement this?
No. I went with absolute minimal changes here. No Gradle, SpringBoot (test) neither.
On Boot, v2.7 is out of support already, but we already test newer version in main branch.
Are there any implications of this pull request? Anything a user must know?
no
Issue
If this PR fixes an open issue, please add a line of the form:
Fixes #Issue
Release notes
Please add a corresponding entry to the file CHANGELOG.adoc