Re: [jetty-users] Examples for SymlinkAllowedResourceAliasChecker in XML

[Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx>]

If a package you are using is itself using a dependency that is EOL then that package should not be upgraded in that version of Debian.

In that version of Debian, that package is forever stuck on the last working version before the EOL hit.

Jetty 9 is now at EOL (End of Life).

There's no Open Source support for Jetty 9 anymore, and it's been this way since June 2022. (see https://github.com/jetty/jetty.project/issues/7958)

There is still Commercial Support for Jetty 9.

- Joakim

On Thu, Jun 26, 2025 at 3:26 AM Fab Stz via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

Given that I'm preparing the Debian package for css-validator (and then for validator.nu), I have to stick with the packages available in Debian. As you can see this has some constraints.

Jetty12 doesn't work in Trixie yet and migration from jetty9 to jetty12 is only planned for forky (maybe due in 2027).

Le 26 juin 2025 09:57:32 GMT+02:00, Andrew McGuinness <andrew@xxxxxxxxxxxxx> a écrit :

June 26, 2025 at 7:21 AM, "Fab Stz via jetty-users" <jetty-users@xxxxxxxxxxx> wrote:

Ok, thank you. I'll try that once jetty12 package works on Debian.

I love Debian stable, and have been using it for over 25 years, but I wouldn't wait on it for Java packages I was developing against. Java is very much its own ecosystem independent of the OS; it's trivial to install a current JVM in /opt and download and run Jetty and whatever other Java applications you need from /usr/local or $HOME

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users