Jakarta Upgrade (Jersey 3, Tomcat 10)#4
Draft
ryanrdoherty wants to merge 65 commits into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 long-term branch embodying changes needed to use Jakarta EE (vs JavaEE) and the associated Jersey 3.x. The merging of this branch to master requires that our website either 1) Upgrade to Tomcat 10+, or 2) Do away with Tomcat entirely and use some other service framework that supports Jakarta EE. Until that happens, we will continue to release both "regular" i.e. JavaEE from master, and Jakarta i.e. from this branch, versions of FgpUtil libs.