Re: [jakarta.ee-spec.committee] Other version mismatches beyond JACC

[David Blevins <dblevins@xxxxxxxxxxxxx>]

Thank you for the reviews and responses.  Looks like we're all aligned.

Kevin, if it's ok I'd love to give Jean-Louis the honor to submit the `RelatedDocuments.adoc` PR for his great work finding these inconsistencies.  That'll give him the honor of being in the commit history even before me :)


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

> On Aug 15, 2019, at 10:40 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
> 
> 
> 
> David Blevins wrote on 8/14/19 2:43 PM:
>> Jean-Louis pointed out to me there are potentially other version mismatches beyond the JACC 1.5/1.6 issue.
>> 
>> Here are the versions we have listed in the Platform spec currently:
>> 
>> - https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/specification/src/main/asciidoc/platform/RelatedDocuments.adoc
>> 
>> ---------------------------------------------
>> 
>> # Jakarta Transactions, version 1.2 vs 1.3
>> 
>> Platform reported version: 1.2
>> PR version: 1.3
>> 
>> We updated the Java Transaction API to create a clean split.  This is in the JCP as 1.3 https://jcp.org/aboutJava/communityprocess/mrel/jsr907/index3.html
>> 
>> Though the actual Java EE 8 version is 1.2, in Jakarta EE 8 we will have 1.3.  I'm reading this as a necessary exception to the rule that all versions would be the same between Java EE 8 and Jakarta EE 8 and what we need to do is update `RelatedDocuments.adoc` to reflect the version is 1.3.
>> 
>> Does anyone disagree?
> 
> Agreed.
> 
>> ---------------------------------------------
>> 
>> # Jakarta™ Deployment Specification, version 1.2 vs 1.7
>> 
>> Platform reported version: 1.2
>> PR version: 1.7
>> 
>> The last maintenance release of JSR-88 on the JCP site is 1.2  https://download.oracle.com/otndocs/jcp/j2ee_deployment-1.2-mrel-oth-JSpec/
>> 
>> Our `RelatedDocuments.adoc` says it is 1.2, but we have a 1.7 in progress for a vote.
>> 
>> What should be our action here?  Update `RelatedDocuments.adoc` to say 1.7, or update the Deployment vote to 1.2?  We have already shipped a 1.7, so it seems we have no choice but to align `RelatedDocuments.adoc` to say 1.7, not 1.2
>> 
>> - https://mvnrepository.com/artifact/jakarta.enterprise.deploy/jakarta.enterprise.deploy-api/1.7.1
> 
> Yes, we screwed up here somewhere, so we're stuck with 1.7 now.
> 
>> ---------------------------------------------
>> 
>> # Jakarta™ Web Services Metadata, version 2.1 vs 1.1
>> 
>> Platform reported version: 2.1
>> PR version: 1.1
>> 
>> At the JCP the latest version is 2.1.  JSR-000181 Web Services Metadata for the JavaTM Platform Maintenance Release 2
>> 
>>  - https://download.oracle.com/otndocs/jcp/websvcs_metadata-2_1-mrel2-eval-spec/
>> 
>> Our `RelatedDocuments.adoc` also says 2.1.  We have a 1.1 up for a vote.
>> 
>> - https://github.com/jakartaee/specifications/pull/48
>> 
>> It looks as though on the JCP side this spec jumped for 1.0 to 2.1 on the first maintenance release and there is no 2.0 or 1.1:
>> 
>> - https://download.oracle.com/otndocs/jcp/web_svcs_md-1.0-fr-spec-oth-JSpec/
>> - https://download.oracle.com/otndocs/jcp/websvcs_metadata-2_1-mrel2-eval-spec/
>> 
>> The claim of 2.1 looks like it was only ever a mistake in the specification itself and the artifact in Maven Central has always been 1.1.
>> 
>> - https://mvnrepository.com/artifact/javax.jws/javax.jws-api/1.1
>> - https://mvnrepository.com/artifact/jakarta.jws/jakarta.jws-api/1.1.1
>> 
>> I'm inclined to say way just update the `RelatedDocuments.adoc` to say 1.1 and leave it at that.
> 
> Agreed.
> 
> (I think we're learning just how carefully this stuff was reviewed at the JCP!)
> 
>> ---------------------------------------------
>> 
>> # Jakarta™ Concurrency Specification, Version 1.0 vs 1.1
>> 
>> Platform reported version: 1.0
>> PR version: 1.1
>> 
>> The last and only official release of JSR 236: Concurrency Utilities for JavaTM EE was 1.0.
>> 
>> - https://download.oracle.com/otndocs/jcp/concurrency-1_0-fr-eval-spec/index.html
>> 
>> However a 1.1 was pushed to the javax.enterprise.concurrent groupId in Maven Central in Feb 2018 and then by us in Jan 19
>> 
>> - https://mvnrepository.com/artifact/javax.enterprise.concurrent/javax.enterprise.concurrent-api/1.1
>> - https://mvnrepository.com/artifact/jakarta.enterprise.concurrent/jakarta.enterprise.concurrent-api/1.1.1
>> 
>> This does not appear to be correct, but I do not know what to advocate.  On the Apache side there is this impl and whatever is decided, I need to know how to bring this in line:
>> 
>> - http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-concurrent_1.0_spec/
>> 
>> Is there simply a version mistake here or are there API changes to the spec we need to implement?
> 
> Good question.  I assume it was just a version mistake.  But it looks
> like we're probably stuck with 1.1 unless we want to do another Maven
> coordinates change.
> 
>> ---------------------------------------------
>> 
>> # Jakarta™ XML Web Services Specification, Version 1.4 vs 2.3
>> 
>> Platform reported version: 1.4
>> PR version: 2.3
>> 
>> This appears to be a clear typo in the `RelatedDocuments.adoc` and it should state 2.3 instead of 1.4.  The latest maintenance release sets the version at 2.3
>> 
>> - https://download.oracle.com/otndocs/jcp/jaxws-2_3-mrel5-eval-spec/index.html
> 
> Agreed.