Re: [jakarta.ee-spec.committee] Two TCK issues for committee discussion

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Scott Stark wrote on 5/31/19 3:04 PM:
> On the additional working group call it was brought up that we have two holes
> in the TCK process that need to be addressed in the weekly spec call are:
> 
> 1. How long after a TCK release does one need to certify new implementations
> against that version. I cannot find the equivalent terms in the JCP or JSPA,
> so perhaps it is part of the TCK license.

It is:
https://jcp.org/aboutJava/communityprocess/licenses/jsr366/SATCK-JSR_366_EE_8-1.0-8.18.14.pdf

> It seems that I have a vague
> recollection of a requirement that new major implementation releases had to
> certify against the latest version of the associated TCKs. I suppose the
> community interest to serve is having implementations synch against the
> latest TCK periodically.

A product/feature release needs to certify with a TCK that is no older
than 180 days.  A maintenance release can continue to use whatever version
of the TCK it originally certified with.

The legal wording in 2.1 is:

(b) Additional Limitations. Except as otherwise set forth in Exhibit A, Licensee
may not:

...

(v) distribute code which has been tested against the TCK and which implements
a substantial portion of the Java Specification unless such code is included
in a Product within the meaning of Section 1.8 and unless, for each new
release of a Product by Licensee, such Product passes, in accordance with
the Documentation (including the TCK Users Guide), the most current TCK
applicable to the latest version of the Java Specification and available from
Oracle one hundred eighty (180) days before FCS of such version of the
Product; provided, however, that if Licensee elects to use a version of the
TCK also provided by Oracle that is newer than that which is required under
this Section 2.1(b)(v), then Licensee agrees to pass such TCK; or

...


(c) Superseded Releases. Oracle agrees that under the following circumstances
the provisions of
Section 2.1(b)(v) above shall not be understood to preclude Licensee from
distributing
maintenance releases (a new release of a preexisting Product that implements
substantially the
same core technologies) of a Product that implemented a prior version of the
Java Specification
("Initial Product") where such maintenance release implements the same version
of the Java
Specification implemented by the Initial Product:

(I won't quote the rest.  Follow the link if you really care.)


That's clear, right?  :-)