Change the JSON-P implementation from Glassfish to Parsson #63
+6 −2
Conversation
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
This was referenced Dec 15, 2021
swallez added a commit that referenced this pull request Dec 15, 2021
swallez added a commit that referenced this pull request Dec 15, 2021
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.
With the move from
javax.jsontojakarta.json, the Glassfish reference implementation of JSON-P has been updated to implement interfaces fromjakarta.jsonbut its class names haven't changed, causing conflicts in environments where thejavax.jsonvariant is present such as JEE8.The
jakarta.jsonvariant of Glassfish is now available under a new name, Eclipse Parsson. This PR updates the dependencies to replace Glassfish with Parsson.Fixes #55