Re: [jgit-dev] Updating jetty, java and moving from javax.servlet to jak

[Mark Waite <mark.earl.waite@xxxxxxxxx>]

On Mon, Apr 22, 2024 at 1:09 PM Matthias Sohn via jgit-dev <jgit-dev@xxxxxxxxxxx> wrote:

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.

I would prefer that it would be 7.0 rather than 6.10 because it will be a breaking change to consumers.  I agree that it is time to start the change.  If not in the next release, then in the release after that.

The Jenkins project is considering its timeline for the Jakarta EE 8 to Jakarta EE 9 transition.  That will include transition from Jetty 10 to Jetty 12, from Spring Security 5.8.x Spring Security 6.x, from Spring 5.3.x to Spring 6.x, and several other transitions.  Jenkins won't make the transition until after Jenkins requires Java 17.  That's planned for October 2024.

 

Mark Waite