[
https://issues.apache.org/jira/browse/HADOOP-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106735#comment-18106735
]
ASF GitHub Bot commented on HADOOP-19912:
-----------------------------------------
joseluisll commented on PR #8653:
URL: https://github.com/apache/hadoop/pull/8653#issuecomment-5373446623
> @joseluisll I was under the mistaken belief that Jetty 12 only supported
jakarta but upgrading to the ee8 version means we can stick with javax and
later switch to jakarta. I'm afraid I have used up my AI credits and it could
be a while until I have some spare to continue work here. I can do some old
fashioned code and review without AI assistance. @pan3793 merged #8654 today. I
can see the benefit in the staged approach in your pdf. Would you have an
interest in trying to progress Stage A?
Added as a subtask: HADOOP-19970 Resolve a single Jetty release and servlet
API on every module classpath:
- Declare Jetty in the modules whose main code uses it.
- Pin the Jetty release carried by the Jersey Jetty test provider.
- Exclude Solr's web stack from the application catalog webapp tests.
- Resolve one servlet API per module.
- Drop the unused JSP API..
The CI Gate and script to check the migration progress and Jetty compliance
is deferred.
> Upgrade to Jetty 12
> -------------------
>
> Key: HADOOP-19912
> URL: https://issues.apache.org/jira/browse/HADOOP-19912
> Project: Hadoop Common
> Issue Type: Task
> Reporter: PJ Fanning
> Priority: Major
> Labels: pull-request-available
>
> See HADOOP-19910 - there is a CVE in Jetty but releases of 9.4 are rare and
> are 'sponsored' - Jetty 9.4 is not actively maintained. There are some
> commercial forks.
> Jetty 12 needs Java 17+.
> Will also force Jersey to upgraded to 3 or 4.
> And to replace many javax classes/jars with their jakarta equivalents.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
