[
https://issues.apache.org/jira/browse/CALCITE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036533#comment-18036533
]
Julian Hyde commented on CALCITE-7284:
--------------------------------------
You fail to acknowledge that Calcite is a library. We are in the middle of the
dependency chain, not at the end of it. We don’t need to “upgrade to JDK 17” -
we’ve supported it since it came out - but you are asking us to force our users
to upgrade.
I hope that most of our users are running the latest Java. I do personally, and
I expect most of them are. I don’t think we should be forcing our users to
upgrade. You - jetty devs - are doing that to us, but FTR it’s not cool.
> 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)
