Dear Jersey Users,
After dedicating over 3.5 years to Jersey 2.x and after more than 70 Jersey releases overall, we are excited to announce the entry into Jersey's next era. After the 2.22 release we have started to work on the new major version - Jersey 3.
There are several motivation factors behind our decision to start working on a new major version of Jersey:
We want to speed up our work related to next revision of JAX-RS specification (JSR-370) and we need to be able to switch Jersey to early builds of the revised JAX-RS API without impacting your ability to uptake new Jersey 2.x releases moving forward.
With Java SE 8 being out of the door for more than 18 months now, we would like to move all parts of Jersey to this most recent Java SE release and be able to fully leverage all the new APIs and language features introduces in Java SE 8. This will help us simplify and refactor core modules, once again, without impacting your ability to uptake the new Jersey 2.x releases moving forward, in case you are not ready to move to Java SE 8 yet.
What does the above mean for the organization of the Jersey project?
A new Jersey 2.x branch <
https://github.com/jersey/jersey/tree/2.x> has been created. This branch remains maintained and evolved and we plan to continue with minor Jersey 2.x updates and releases.
The Jersey master branch <
https://github.com/jersey/jersey> has been switched to 3.0-SNAPSHOT version, and the project build has been switched to Java SE 8 or later. Few additional refactorings necessary for full switch to Java SE 8 in the project has been made too. Over time, we plan to switch this branch to uptake the early builds of JAX-RS 2.1 API.
May the REST be with you,
Marek & The Jersey Team