Fwd: Updating jetty, java and moving from javax.servlet to jakarta.servlet

[Matthias Sohn]

FYI

---------- Forwarded message ---------
From: Matthias Sohn <matthi...@gmail.com>
Date: Mon, Apr 22, 2024 at 9:09 PM
Subject: Updating jetty, java and moving from javax.servlet to jakarta.servlet
To: JGit Developers list <jgit...@eclipse.org>

Hi,

I think it's time to consider some major updates

• community support for jetty 9, 10 and 11 ended, hence we should update to jetty 12
  see https://github.com/eclipse-jgit/jgit/issues/41
• jetty 12 requires Java 17, meanwhile the current LTS is 21 hence I think it's time to bump the minimum Java version to 17
• I think it's also time to update from javax.servlet to jakarta.servlet 3 years after this change was done upstream when Eclipse Jakarta became the successor of Oracle's JEE
  see https://github.com/eclipse-jgit/jgit/issues/19 and
  https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/
• we need to decide if we release these updates in 6.10 or if we better rename the next release to 7.0.

Please provide feedback on these proposed updates.

-Matthias

[David Ostrovsky]

Thanks for starting this discussion.

I think we should take this upgrade path:

Jetty 9.x => Jetty 10.x => Jetty 11.x => Jetty 12.x

During the upgrade to Jetty 11.x we should migrate to jakarta.servlet and servlet-api 5.x and

migrate off javax.inject dependency, that would allow us to upgrade to Google Guice 7.0.

I've tried the upgrade to Jetty 11 already. Here is the JGit change: [1] and the Gerrit series: [2].

I've also updated the affected gerrit plugins except gitiles-plugin, that relies on gitiles-servlet

(it looks good, only some binding tests are failing).

A good question is: would all Gerrit stack holders support this migration path?

[1] https://review.gerrithub.io/c/eclipse-jgit/jgit/+/189213

[2] https://gerrit-review.googlesource.com/q/topic:jakarta.servlet

-Matthias