SapMachine (25) #2231: Backport JDK-8350481 to fix liquibase issues#2232
Open
GoeLin wants to merge 1 commit intosapmachine25from
Open
SapMachine (25) #2231: Backport JDK-8350481 to fix liquibase issues#2232GoeLin wants to merge 1 commit intosapmachine25from
GoeLin wants to merge 1 commit intosapmachine25from
Conversation
Member
|
Hello @GoeLin, this pull request fulfills all formal requirements. |
Member
|
Generally looks good. However, for clean OpenJDK backports it would be preferred if you keep the OpenJDK commit message. E.g take exactly the result of a git cherry-pick ... |
e00c6fc to
8cfb4f5
Compare
Member
|
Hello @GoeLin, this pull request fulfills all formal requirements. |
Member
Author
|
Fixed commit message. |
RealCLanger
approved these changes
May 8, 2026
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
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.
Backport 8196182: ServiceLoader.iterator().hasNext()/.next() may throw a LinkageError as
we see intenal usages running into this error.
Clean backport, tests pass.
fixes #2231