[WFLY-16264] Minor follow up to the Jakarta JSON Processing upgrading… #15431
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
…. The implementation module should not export the services to avoid a regression if users include an implementation in their deployment. https://issues.redhat.com/browse/WFLY-16264 Signed-off-by: James R. Perkins <jperkins@redhat.com>
github-actions
bot
added
the
deps-ok
bstansberry
approved these changes
Apr 14, 2022
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.
…. The implementation module should not export the services to avoid a regression if users include an implementation in their deployment.
Follows up on #15423
https://issues.redhat.com/browse/WFLY-16264
This is a minor update to revert to the previous behavior of relying the API loading the hard-coded default provider. By exporting the services from the implementation it will be found before any implementation provided in the deployment. Whether or not this is the behavior expected, it's how we've done it in the past.