Closed joakime closed 1 month ago
I was wondering if anybody had thoughts on this.
I agree we should update to a supported jetty version. I started looking into your change but stalled since I am currently swamped with other stuff at $DAYJOB
When we are at this we should consider to also update
javax.servlet
to jakarta.servlet
(issue #19)I asked for feedback from the community on the jgit list here https://www.eclipse.org/lists/jgit-dev/msg04235.html
Note, you can use javax.servlet
on Jetty 12 via the ee8
environment.
Update to
JGit releases (existing and planned) are listed here https://projects.eclipse.org/projects/technology.jgit
The next release 6.10 is planned to be shipped with Eclipse IDE 2024-06 on June 12, 2024. We plan to ship the update to Jetty 12 (see issue 41) with JGit 7.0 with Eclipse IDE 2024-06 on Sep 11, 2024.
servlet API was updated to jakarta.servlet 6.1.0 in https://eclipse.gerrithub.io/c/eclipse-jgit/jgit/+/1200138
closing since changes were merged and shipped with 7.0.0 on Sep 11
Version
All
Operating System
Linux/Unix
Bug description
jgit is still using an End of Community Support version of Jetty.
See:
Actual behavior
Not possible to use the only supported version of Jetty at the moment.
Expected behavior
Upgrade to Jetty 12.
Note: if you want to stick with the
javax.servlet
namespace, then use theee8
environment on Jetty 12.Relevant log output
No response
Other information
No response