Jetty versions supported - fix vulnerabilities #15010
Replies: 2 comments
-
|
@wheestermans31 Please see the pinned issue here: #13918, where this is explained in more detail. I also wrote a blog a while back. Briefly, for others that come across this issue: yes, EOL releases are still supported by the Jetty developers at Webtide and through their partners Herodevs and Tuxcare. Older versions of Jetty will be supported indefinitely through these paid support channels. As for migration, Jetty 12.1 is the recommended target if you require updated CVE support while relying on the open-source project. Moving forward, the Jetty project will support the current and previous releases (12.1 and 12.0 at the time of this response). Once Jetty 13.0 releases with the latest specification update from Jakarta EE, support for Jetty 12.0 will fall back to EOL support options. |
Beta Was this translation helpful? Give feedback.
-
For these older EOL versions of Jetty, see
Note: https://jetty.org/docs/jetty/12.1/index.html If you want to migrate to Jetty 12, and maintain the EE level for each migration you can use the appropriate environment on Jetty 12 that best matches your webapp.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Jetty Version
Jetty 9.4
Jetty 10
Jetty 11
Question
If we have projects still using one of the above versions, do they need to move now to Jetty 12, or does these still receive vulnerability fixes.
What is, if needed, the easiest way of working to migrate:
9.4 --> jetty 12
10 --> jetty 12
11 --> jetty 12
Beta Was this translation helpful? Give feedback.
All reactions