Migrate to Jakarta EE 10 and Jetty 12 #3730
Merged
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.
Description
Performs the migration from Java EE to Jakarta EE 10 (see here for background).
This migration is crucial to prevent the Dependency-Track code base from falling behind, and accumulating too much tech debt. Major frameworks like Spring and Quarkus migrated to Jakarta EE years ago.
This also upgrades the embedded Jetty from 10 to 12. 12 being the latest, and only community-supported version of Jetty:
(Source)
Addressed Issue
Closes #2727
Additional Details
Depends on stevespringett/Alpine#570
Checklist
This PR fixes a defect, and I have provided tests to verify that the fix is effectiveThis PR implements an enhancement, and I have provided tests to verify that it works as intendedThis PR introduces changes to the database model, and I have added corresponding update logicThis PR introduces new or alters existing behavior, and I have updated the documentation accordingly