refactor: update provider name to be more compatible with Jakarta Config #561
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
|
Can one of the admins verify this patch? |
otaviojava
approved these changes
Dec 13, 2024
|
Thank you Keyle |
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.
Upon doing a retrospective on #559 it was pointed out to me that if Jakarta Config is accepted into Jakarta EE 12 then using the
@Repositoryprovider attribute ofEclipse JNoSQLmight be problematic if that attribute is configurable using Jakarta Config. If Jakarta Config follows the Microprofile Spec the space should not be an issue, but we could avoid potential issues by transitioning toEclipse_JNoSQLor something without a space.I'm also open to suggestions.