Hi Marek, Markus,
Thanks a bunch for the clarification. Much appreciated.
Regards
Nasir
- Nasir
On Mon, Oct 5, 2015 at 1:03 AM, Marek Potociar <marek.potociar_at_oracle.com>
wrote:
> Hello Nasir,
>
> In terms of Jersey specific features and extensions, Jersey 3.0 will
> remain to evolve in a backward compatible way as much as possible. While
> there may be some incompatibilities introduced if necessary, we do not
> expect major disruptions similar to those when switching from Jersey 1.x to
> Jersey 2.x in the most commonly used features.
>
> As for JAX-RS API, this will remain fully backward compatible. This is
> mandated for any Java EE specification.
>
> HTH,
> Marek
>
> On 02 Oct 2015, at 17:57, Nasir Rasul <nasir.rasul_at_gmail.com> wrote:
>
> Hi All,
> That's great news. Will there be backward compatibility? or it is expected
> that it will essentially be a new release?
>
> What are the features which release 3 will target?
> i.e JSR-370 - Jersey 2.2 = {what set of features?}
>
>
> Thanks
> Nasir
>
> - Nasir
>
> On Fri, Oct 2, 2015 at 5:48 AM, Markus Karg <karg_at_quipsy.de> wrote:
>
>> Dear Jersey Team,
>>
>>
>>
>> making use of Java 8 and beginning work on JAX-RS 2.1 are great news! J
>>
>>
>>
>> -Markus
>>
>>
>>
>>
>>
>> *Von:* Marek Potociar [mailto:marek.potociar_at_oracle.com]
>> *Gesendet:* Freitag, 2. Oktober 2015 14:46
>> *An:* Users
>> *Betreff:* [Jersey] Announcing start of work on Jersey 3.0
>>
>>
>>
>> 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
>>
>
>
>