eclipse-ee4j
Jersey 4.0.x release
Hi Jersey maintainers,
with Jakarta EE 11 now released (in June 2025), do you have any estimated timeline for Jersey 4.0.x compatibility with the new Jakarta EE 11 version?
Just trying to plan our upgrade path - completely understand if timelines are still being worked out!
Found some pointers here:
- https://github.com/eclipse-ee4j/jersey/wiki/Road-Map#released-40x
- https://github.com/eclipse-ee4j/jersey/milestone/94?closed=1
It may also be related to the release of Jersey 3.1.x (#5934).
Thanks for all your great work!
We apologize for the situation. Currently, the release process has been disabled for Jersey, and we are working on a replacement within the community-shared Eclipse infrastructure. It is hard to set an estimate. It can be the next month, but it might also be September.
Here are more details - the difficulty lies in properly configuring the Eclipse continuous integration to use the new Portal user tokens.
Thank you for the update and transparency regarding the Jersey release timeline. We understand that transitioning to the Eclipse infrastructure involves complexities that are difficult to predict precisely.
We appreciate the community's efforts in working toward this solution. Please keep us informed of any significant developments, and don't hesitate to reach out if there's any way we can support the process.
@jansupol
Is it working now? I saw this commit
https://github.com/eclipse-ee4j/jersey/commit/b25faa21671b7e4dc1355d6c8f86a65a5b6f1451
and this one is green:
https://ci.eclipse.org/jersey/view/EE8,%20EE9,%20EE10,%20EE11%20Release%20Jobs/job/release_to_central/job/Jersey-EE10-main_release/
Do you have any post-mortem of what was exacly done to get it working again? (assuming that it now works)
Hi @arjantijms, I'm taking the word to answer - the commit you are referring to is to fix the release 3.1.11 process. And the job result is for the 3.1.11 version. However, there are some issues with TCK and the 3.1.11 version. Now I'm solving this. After TCK tests pass OK for 3.1.11, it will be published to Maven Central. However, this is all for the 3.1.x which is Jakarta EE10. The version 4.0.0-M3 (EE11) will be prepared just after 3.1.11 is in the central.
I would be grateful if you could provide an update on the current status of 4.0.0-M3 and 4.0.0, as version 3.1.11 (see also https://github.com/eclipse-ee4j/jersey/issues/5934) was released about three weeks ago.
3.1.11 is already available on maven central. However, 4.0.0-M3 is not available there.
Hi,
Jersey support has been removed from Spring Boot 4.x milestone releases https://github.com/spring-projects/spring-boot/issues/47017 because they aren't certain when 4.0.0 GA will be announced. Our team needs to plan accordingly as we use Jersey in conjunction with Spring Boot and are unable to test quite a few of our applications currently.
Would you be able to provide any clarity on 4x GA timeline? Our primary goal is to know if it will be included in Spring Boot 4x GA in November, 2025.
Hi @cmakinen, an effort was made to modularize the 4.0 version. Now there is the 4.0.0-M4 available with JPMS support. When it is proven that the M4 works and there are no complaints from the community, the M4 will be transformed into the 4.0.0 release.
Hi @senivam,
I'm about to try 4.0.0-M4, especially the JPMS support. One thing that I observed:
The dependency org.glassfish.jersey.media:jersey-media-json-jackson misses either a module descriptor or an automatic module name entry in META-INF/MANIFEST.MF.
Will that be added?
@senivam For GlassFish M4 works pretty well. What do you think, shall we transition M4 to final?
Thanks for finishing and releasing Jersey 4.0.0!
By the way https://github.com/spring-projects/spring-boot/issues/47967 support for Jersey was restored for Spring Boot 4.x now that Jersey supports JAX-RS 4 (Jakarta EE 11) and Jersey 4.0.0 was released.
Should this issue be closed by the maintainers (@senivam / @jansupol)? Or should I close this issue?
@mjschwaiger Do you know if anyone from the Spring team might be interested or capable of donating resources / contributions to Jersey (e.g. helping with its maintenance and further development)?
@mjschwaiger Do you know if anyone from the Spring team might be interested or capable of donating resources / contributions to Jersey (e.g. helping with its maintenance and further development)?
@arjantijms Sorry, I’m not part of the Spring team, so I can’t really give any details on that. I just noticed the issues related to Spring Boot 4 and wanted to point out that the latest Jersey release came out just in time for the Spring Boot 4 launch.