[
https://issues.apache.org/jira/browse/HADOOP-19625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007291#comment-18007291
]
Palakur Eshwitha Sai edited comment on HADOOP-19625 at 7/15/25 5:15 PM:
------------------------------------------------------------------------
Jersey 3.x uses the *Jakarta* namespace, which introduces some compatibility
considerations with Jetty versions:
* *Jetty 9.x* is *EOL* and must be upgraded.
* *Jetty 12 EE8* supports the legacy *{{javax}}* namespace.
* *Jetty 12 EE10* supports the newer *{{jakarta}}* namespace.
>From my initial work on the patch, here's how Jersey versions map to Jetty:
* *Jersey 3.0.x* requires {*}Jetty 11{*}, which has also reached *EOL* and is
no longer community-supported.
* *Jersey 3.1.4+* requires {*}Jetty 12 EE10{*}, aligning with the *Jakarta
namespace* and offering long-term support.
Reference: [Jersey Migration
Guide|https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest31x/migration.html#mig-3.0.0]
Related prior work: [Hadoop PR #7130|https://github.com/apache/hadoop/pull/7130]
Given that both Jetty 9 and 11 are EOL, and that Jersey 3.1.4+ requires EE10,
the cleaner long-term approach would be to migrate directly to {*}Jersey 3.1.4+
with Jetty 12 EE10 (requires JDK 17){*}.
Would like to confirm if this is the right direction before proceeding further.
Kindly provide your inputs on the same [[email protected]], [~fanningpj]
was (Author: JIRAUSER302593):
Jersey 3.x uses the *Jakarta* namespace, which introduces some compatibility
considerations with Jetty versions:
* *Jetty 9.x* is *EOL* and must be upgraded.
* *Jetty 12 EE8* supports the legacy *{{javax}}* namespace.
* *Jetty 12 EE10* supports the newer *{{jakarta}}* namespace.
>From my initial work on the patch, here's how Jersey versions map to Jetty:
* *Jersey 3.0.x* requires {*}Jetty 11{*}, which has also reached *EOL* and is
no longer community-supported.
* *Jersey 3.1.4+* requires {*}Jetty 12 EE10{*}, aligning with the *Jakarta
namespace* and offering long-term support.
Reference: [Jersey Migration
Guide|https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest31x/migration.html#mig-3.0.0]
Related prior work: [Hadoop PR #7130|https://github.com/apache/hadoop/pull/7130]
Given that both Jetty 9 and 11 are EOL, and that Jersey 3.1.4+ requires EE10,
the cleaner long-term approach would be to migrate directly to {*}Jersey 3.1.4+
with Jetty 12 EE10 (requires JDK 17){*}.
Would like to confirm if this is the right direction before proceeding further.
> Migrate from Java to Jakarta - Upgrade to Jersey 3.x, Jetty 12.x
> ----------------------------------------------------------------
>
> Key: HADOOP-19625
> URL: https://issues.apache.org/jira/browse/HADOOP-19625
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Palakur Eshwitha Sai
> Priority: Major
>
> This Jira is to track the migration of Javax to Jakarta in Hadoop and
> identify all the transitive dependencies which need to be migrated as well.
> Currently, I see the following major upgrades required:
> # Jersey: 2.46 to 3.x
> # Jetty: 9.x to 12.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
