add second artifact with support for Jakarta EE through eclipse transformer #53
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
normankrueger
approved these changes
Feb 24, 2023
pheyken
changed the title
|
Hi thank you for the details, we are probably moving from Jersey as our HTTP client which was probably an overkill for a simple HTTP library like ours. This should also resolve the javax namespace problem and remove the need for transformer. |
|
Thank you very much! |
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.
There are already discussion about migrating from javax to jakarta (#47 & #35).
This would however create a second artifact with support for Jakarta which could be included by the user of the library as needed while still maintaining backward compatibility for now.