Control: tags -1 - moreinfo
On 24/04/2025 19:14, Paul Gevers wrote:
I agree it's too late for a full transition to Jetty 12, but several
packages only use jetty9 to run unit tests or for minor features. The
idea is to leave them as-is for Trixie, remove the jetty9 server
package but keep the libjetty9-java library.
I know it doesn't help anything to ask, but why wasn't this done before
the freezes?
I noticed the Jetty 9 EOL at the end of January and rushed to complete
the Jetty 12 packaging. It took quite some time to prepare because it
required several new packages (9 jakarta-* packages and libslf4j2-java)
and then the package stayed nearly 2 months in the NEW queue. I expected
it would migrate before the freeze.
- eclipse-equinox and eclipse-platform: the lack of jetty12 blocks the
upgrades, the packages lag 1.5 year behind upstream releases.
So your idea is to upgrade those packages now? That doesn't really sound
in line with the current freeze: "only small, targeted fixes are
appropriate for trixie."
The Eclipse packages are fairly straightforward to update usually, but I
can hold the upgrade until Forky. The package I'd like to update in
priority is eclipse-jdt-core, which provides the JSP compiler used by
Tomcat. The current version (4.29) supports only Java 19, ideally it
should be aligned with the default Java version in Trixie, which is Java
21. This version started being supported in Eclipse 4.30. That's a more
targeted update than a full upgrade to Eclipse 4.35.
- lucene9: Jetty is used for unit tests only (libjetty9-java should be
removed from the package dependencies)
Have bugs been filed already?
Not for lucene9, I just noticed it today as I reviewed the reverse
dependencies.
- trapperkeeper-webserver-jetty9-clojure: specific to Jetty 9, Puppet
hasn't upgraded Jetty yet and will stick to Jetty 9 in Trixie.
It doesn't require the server part I understand?
I requires the library, but not the jetty9 "daemon" package. This one
must be removed before the release.
Allowing jetty12 in Trixie would enable us to have up to date Eclipse
packages and a recent and supported version of the Jetty server, on
par with the Tomcat package. The risk of regression is limited because
the full transition will not happen before Forky.
What is still left with for "full transition"?
Replacing libjetty9-java with libjetty12-java everywhere, which is a
little more than switching the paths to a few jar files because Jetty 12
transitioned from the javax to the jakarta namespace and the API
changed. We'll have to send patches upstream, this is likely to take
some time and the Java Team will tackle that task in Forky.
Emmanuel Bourg
