Include JDK17 in OMR coordinated merge documentation - #16004
Merged
Conversation
Signed-off-by: Daryl Maier <maier@ca.ibm.com>
Contributor
Author
|
@pshipton : would you mind merging? I only added JDK17 to the list of build targets for the OMR acceptance build. The rest of the changes are automatic whitespace removal at end-of-lines. |
pshipton
approved these changes
Sep 28, 2022
Member
|
I expect it will become important to check a more recent version as well, i.e. jdk19 or later, once it's ready. But that can be added later. The OMR acceptance build doesn't consider it now. |
Member
We are getting closer for jdk19, I'll modify the acceptance build now and we can see how it goes. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Signed-off-by: Daryl Maier maier@ca.ibm.com