Dear Jersey users,
Jersey is a successful open-source project that has been evolving in it’s 1.x version since 2007. Later, by the end of 2011 we started to work on the next major update of Jersey - version 2.0, which was released in May of 2013 with support for JAX-RS 2.0 that brought standardization into many areas, where Jersey 1.x was only offering proprietary support, including client API, request and response filters etc. Since then, Jersey 2.x has been our primary development focus and it has started to replace Jersey 1.x in many deployments, products and frameworks. Currently, the vast majority of Jersey users are developing their applications with JAX-RS 2.0 APIs and run their code on Jersey 2.x releases and we encourage all the remaining Jersey 1.x users to move to Jersey 2.x too.
Moving forward we want to focus as much effort as possible to evolving and maintaining Jersey 2.x code base. In order to do that, we had to make a decision about future investments into Jersey 1.x code base. After carefully considering all the options, we have decided to fully focus on Jersey 2.x. As a result we are now putting Jersey 1.x development on hold and moving Jersey 1.x code base into sustaining mode. This means that we will be still addressing any reported security issues as well as any Jersey-related issues reported by customers of Oracle-supported products that ship Jersey. All other reported issues will be only considered for fixing in Jersey 2.x code base.
So what does it mean for you?
If you have not done so yet, please consider migrating your code to Jersey 2.x. Today, Jersey 2.x is a stable, robust and high performance platform with many additional features that are not available in Jersey 1.x. It is also the primary REST web services platform that will be supported in future Oracle products.
When it comes to reporting issues, in case you would like to report a new issue experienced with Jersey 1.x, please verify that the same issue applies to Jersey 2.x before reporting the issue, to prevent a possibility of your issue being rejected (with exception of runtime security issues, of course). I’d like to also mention that recently, we did a clean up of our open Jira issues and as part of it, we have already rejected a number or issues (bugs, improvements and features) reported specifically against Jersey 1.x code base. As with any such cleanup, we could have made a mistake and could have rejected your issue even though it may also apply to Jersey 2.x code base. In case you are aware of any such issue, please feel free to open a new issue against Jersey 2.x with the same content. We sincerely apologize for any inconvenience caused here.
Thank you for your understanding,
Marek Potociar