Repository navigation
[improve][build] Upgrade Jersey to 3.1.12 - #26347
Merged
Merged
Conversation
Upgrades Jersey from 3.1.10 to the latest 3.1.x patch release, 3.1.12. Stays on the 3.1.x line deliberately: Jersey 4.x implements jakarta.ws.rs-api 4.0 (Jakarta EE 11), which would force a Jakarta major version bump and diverge from the Jetty 12.1 ee10 environment that Pulsar targets. All nine Jersey modules in the version catalog share the single 'jersey' version reference, and 3.1.12 is published for every one of them, so no per-module pin is needed. Assisted-by: Claude Code (Opus 5)
nodece
approved these changes
Aug 18, 2026
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.
Motivation
Jersey in the version catalog is at 3.1.10, while 3.1.12 is available. This picks up two patch
releases of the JAX-RS implementation used by the broker, proxy, websocket and admin client REST
layers.
Jersey 4.x is deliberately not taken here. Jersey 4 implements
jakarta.ws.rs-api4.0, which isJakarta EE 11. Pulsar's REST stack is currently aligned to Jakarta EE 10 —
jetty-ee1012.1.12 pinsjakarta.servlet-api6.0.0, and the catalog pinsjakarta.ws.rs-api3.1.0 — so moving Jersey to 4.xwould force a Jakarta major version bump across the whole REST and servlet stack. That is a separate,
much larger change.
Modifications
gradle/libs.versions.toml:jersey3.1.10 → 3.1.12.LICENSE.bin.txtfiles.All nine Jersey modules referenced in the catalog share the single
jerseyversion reference, and3.1.12 is published for every one of them (including
jersey-container-servlet-core), so noper-module version pin is needed.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Verified locally with:
./gradlew sanityCheck— compiles every module's main and test sources./gradlew checkBinaryLicense— confirms the LICENSE entries match the jars actually bundled inthe server and shell distributions
Does this pull request potentially affect one of the following parts: