You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 is a draft PR for an attempt to migrate to Jakarta EE.
There are two main issues:
https://resteasy.github.io/2020/01/15/resteasy-3100final-jakarta/ and
https://resteasy.github.io/2019/10/30/resteasy-440final-moving-to-jakarta-artifacts-and-much-more/ claim to move to Jakarta APIs but it seems it is just about using jakarta groupId but the package names in 4.6.0 are still javax.**. I've tried to work it around by using temporary custom javax classes that delegate to the jakarta impls but it is not finished.