Apply same fix from platform-tck#2463 to Persistence TCK#755
Merged
scottmarlow merged 1 commit intoNov 20, 2025
Conversation
Member
|
@scottmarlow One for you. |
This comment was marked as outdated.
This comment was marked as outdated.
scottmarlow
approved these changes
Nov 20, 2025
Member
|
Note this is for addressing #637 as well |
Member
|
Thanks @kuuku123! |
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
3 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.
This change copies the fix from jakartaee/platform-tck#2463
into the standalone Persistence TCK.
It resolves the same issue that was previously addressed in the Platform TCK’s persistence-outside-container tests.
The purpose is to keep both TCK sources consistent while the Persistence TCK transition is underway.