[
https://issues.apache.org/jira/browse/CALCITE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080124#comment-18080124
]
Ian Bertolacci commented on CALCITE-7284:
-----------------------------------------
I'm hoping we can find a path to moving away from EOL Jetty.
Upgrading to Jetty 12 does drop JDK8 support, but multiple JDK suppliers are
sunsetting JDK8: [OpenJDK8 support ends in November
2026|https://access.redhat.com/articles/1299013], and others
([oracle|https://www.oracle.com/java/technologies/java-se-support-roadmap.html],
[azul|https://www.azul.com/products/azul-support-roadmap/]) end 2030. So,
these JDK8 users will likely be moving away from JDK8 anyways.
A middle-ground might be to support two Avatica codelines: one for jetty-9, and
one for jetty-12. My understanding is that the Jetty 12 EE8 API provides a
similar API to Jetty 9, which should reduce code differences. Since 2020,
Avatica only has 30-40 commits per year, so juggling the two may not be as
painful as it first seems.
Alternatively, Avatica could move away from Jetty entirely. However, that would
require users to adopt those new APIs (which is also a problem for a Jetty
Upgrade). Additionally, the libraries that support JDK8 are likely also being
sunset (such as [Tomcat 9, which will EOL in March
2026|https://tomcat.apache.org/tomcat-9.0.x-eos.html]), and we'll have to start
all over again.
There may be (and likely are) better ideas; but ultimately, some decision will
need to be made about what Avatica uses as its network/server foundation.
> Jetty 9 is EOL, Upgrade to Jetty 12
> -----------------------------------
>
> Key: CALCITE-7284
> URL: https://issues.apache.org/jira/browse/CALCITE-7284
> Project: Calcite
> Issue Type: Task
> Reporter: Joakim Erdfelt
> Priority: Major
>
> Jetty 9.x has been fully EOL since Jan 1, 2025.
> Jetty 10 and Jetty 11 have also been EOL since Jan 1, 2025.
> Jetty 12 is the only Open Source supported version of Jetty right now.
> If you need `javax.servlet.` (the legacy namespace) support, you can continue
> to use that on Jetty 12 and it's `ee8` environment.
> For more information about the status of EOL versions of Jetty see.
> [https://github.com/jetty/jetty.project/discussions/13984]
>
> Yes, this means you have a JDK minimum of JDK 17.
> JDK 8 support is a dead end today, more and more open source projects have
> abandoned JDK 8 support, and you are subject to an ever increasing array of
> never to be fixed CVEs due to your project's desire to stick with JDK 8 as a
> minimum support level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
