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.