Well, let me educate you the way I was educated a few days back :)
JAX-RS spec consists of:
- JAX-RS spec document
- JAX-RS API javadoc
- JAX-RS API signatures (but not any code in the API classes!)
JAX-RS RI consists of:
- any code inside JAX-RS API classes (yes, JAX-RS API jar is actually a product of RI, not the spec!)
- any other RI code (in our case Jersey) that is required to pass JAX-RS TCK and Java EE CTS.
Now that we know, who is who, the rules are simple:
- We need to do a JAX-RS errata MR, whenever we make changes to the spec that do not break TCK or change APIs. A JAX-RS errata MR does not change JAX-RS version - only adds new "revisions".
- We would need to bump up the spec version only if we made changes to the API or made any other incompatible changes in spec or TCK.
- We do not need to do MR whenever we only fix RI without impacting the spec.
So, what we're doing now is the following:
- we're doing a JAX-RS errata MR for the javadoc changes we made as part of the bug fixes. The result will be updated javadoc and JAX-RS 2.0 "Rev a". I.e. still JAX-RS 2.0, not JAX-RS 2.0.1...
- we've also made changes to the code inside API classes, which is technically a change in JAX-RS RI. This change will result in a release of a new JAX-RS API JAR. This jar has a version 2.0.1, but it is not version of JAX-RS, it is a version of the binary file (that is released and maintained as part of RI).
That's as simple as it gets ;-)
Marek
On 28 Aug 2014, at 17:45, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
> On 28/08/14 16:38, Marek Potociar wrote:
>> If at all possible, in the current situation where new JAX-RS binaries are already in maven central, I would prefer to not make any more changes to the release unless absolutely necessary.
>>
>> So I guess it depends a bit on how strongly you want to push for including these 2 API docs changes in the current release. To ask differently - can this wait for e.g. 2.0.2? :)
> Absolutely, 2.0.2 or 2.0.x in general would be fine. I even commented there that 2.0.2 would be a good target if the issues were accepted, I just thought having this MR process meant that we'd have 2.0.2 out at the end of it :-).
>
> Thanks, Sergey
>
>>
>> Marek
>>
>> On 27 Aug 2014, at 22:45, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>>
>>> Hi Marek
>>>
>>> No problems. If you can please address
>>>
>>> https://java.net/jira/browse/JAX_RS_SPEC-483
>>> and may be
>>> https://java.net/jira/browse/JAX_RS_SPEC-482
>>>
>>> JAX_RS_SPEC-483 at least,
>>>
>>> if it is too late them commenting at those JIRA issues would be welcome
>>>
>>> Sergey
>>>
>>>
>>> On 27/08/14 18:25, Marek Potociar wrote:
>>>> Hello experts,
>>>>
>>>> Let me take back my previous announcement, it looks like it was a bit
>>>> premature. Because of the fact that the changes include minor javadoc
>>>> clarifications, we have to go through an official MR process for this
>>>> release.
>>>>
>>>> The MR review process has been started:
>>>> https://jcp.org/aboutJava/communityprocess/maintenance/jsr339/index.html
>>>>
>>>> We should be able to officially release the JAX-RS 2.0.1 by the end of
>>>> September.
>>>>
>>>> Thank you and sorry for any confusion.
>>>> Marek
>>>>
>>>> On 13 Aug 2014, at 16:11, Marek Potociar <marek.potociar_at_oracle.com
>>>> <mailto:marek.potociar_at_oracle.com>> wrote:
>>>>
>>>>> Hello experts,
>>>>>
>>>>> A bug-fix release for JAX-RS 2.0 has been released as version 2.0.1.
>>>>> So far, you can find the released bits available for download in the
>>>>> central maven repository:
>>>>>
>>>>> binaries:
>>>>> http://search.maven.org/remotecontent?filepath=javax/ws/rs/javax.ws.rs-api/2.0.1/javax.ws.rs-api-2.0.1.jar
>>>>> javadoc:
>>>>> http://search.maven.org/remotecontent?filepath=javax/ws/rs/javax.ws.rs-api/2.0.1/javax.ws.rs-api-2.0.1-javadoc.jar
>>>>> sources:
>>>>> http://search.maven.org/remotecontent?filepath=javax/ws/rs/javax.ws.rs-api/2.0.1/javax.ws.rs-api-2.0.1-sources.jar
>>>>>
>>>>> We're still working on making the artifacts available also via JCP
>>>>> JSR-339 page. The official updated RI will be made available later
>>>>> next week when Jersey 2.12 is released.
>>>>>
>>>>> Thank you,
>>>>> Marek
>>>>
>>>
>>
>