[
https://issues.apache.org/jira/browse/HADOOP-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101346#comment-18101346
]
ASF GitHub Bot commented on HADOOP-19912:
-----------------------------------------
pan3793 commented on PR #8653:
URL: https://github.com/apache/hadoop/pull/8653#issuecomment-5165742249
> this is targeted at 3.6.0. I have no intention of seeing this backported
to 3.5.
@pjfanning I also suppose so.
> It's not really feasible to split these into separate upgrades.
I actually mean the opposite thing - as you know, Java/Jakarta EE is
composed of a lot of components, we should upgrade them all (use Spring as an
example, Spring Framework 6.0 migrated to Jakarta EE 9 entirely), or none,
otherwise, it might put downstream projects that pull Hadoop as a dependency in
an awkward situation
> Upgrade to Jetty 11 or 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]
