Hi,
Based on the feedback (thanks it was most useful) I propose the
following:
The solution that will cause the least amount of confusion is for
the version of Jersey after 1.1.5 to be 1.2 [*].
It looks like we were living in an ivory tower w.r.t. the Jersey
version being in sync with the JAX-RS version :-)
Paul.
[*] Any new major version release of JAX-RS will also result in a new
major release of Jersey.
On Jan 8, 2010, at 1:47 PM, Paul Sandoz wrote:
> Hi,
>
> We plan to release Jersey 1.1.5 on the week on Jan 18th.
>
> Jakub is working hard on the OSGi stuff but we want to make sure we
> get it right, and it might require some more soak time in the trunk
> (currently it is in a branch) for other developers to have a play
> with and provide feedback.
>
>
> After that release i am proposing to change the versioning scheme of
> Jersey. Currently we retain the first two numbers as the major and
> minor version of the JAX-RS API Jersey implementations. This is not
> ideal:
>
> 1) Jersey has it's own API that evolves separately it makes it
> harder to signal major, minor, micro status of Jersey itself;
>
> 2) The current versioning scheme does not work very well with maven
> and OSGi, for example 1.1.4.1; and
>
> 3) Then we can consider Markus recommendations for declaring version
> ranges for dependencies.
>
>
> I have been advised that to avoid confusion with the JAX-RS version
> we should choose a version of Jersey that is clearly different. Thus
> i propose that we start the next version at 3.0, even though of
> course it does not really represent a major change.
>
> Paul.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>