OpenJDK Community TCK and EA TCK License Agreement V 3.0
volker.simonis at gmail.com
Tue Oct 24 08:12:30 UTC 2017
I have some questions regarding the new "OpenJDK Community TCK and EA
TCK License Agreement V 3.0" .
In the "RECITALS" section, what exactly does "Java SE 9 Specification
(or later, as indicated by Oracle in writing to you)" mean?
1. Does the new license agreement V 3.0 also cover upcoming version of
the Java SE TCK (i.e. 18.3, 18.9)?
That would be actually nice because it would free us from going
through this process every six month now. On the other hand, how can
"as indicated by Oracle in writing to you" be interpreted?
2. Will Oracle automatically contact every signatory if new versions
of the TCK will become available and grant them the rights to use the
new versions as well?
If question 2 will be answered with "Yes", there's a problem with
section "7.0 TERM AND TERMINATION" which defines the term of the OCTLA
with respect to "Effective Date" which is the date the initial OCTLA
was submitted and signed. So for subsequent versions, the term will
become shorter and shorter.
3. Shouldn't the term of the OCTLA be defined with respect to the
first general availability date of a TCK?
Otherwise signatories who sign it later will get longer access
compared to early singers. It could also lead to multiple singing
requests. I.e. I could sign the OCTLA for JDK 8 once again now in 2017
to get another 3 + 5 years coverage in addition to the 3 + 5 year I
got in 2014 when I singed it the first time.
>From the "RECITALS" section and the definition of "EA TCK" as
"pre-release version of the TCK subsequent to the most generally
available version of the TCK" I understand that a successful signing
of OCTLA V 3.0 gives me access to all the subsequent version of EA
4. Is it correct that a successful signing of OCTLA V 3.0 gives me
access to all the subsequent version of EA TCKs?
If question 4 will be answered with "Yes" there's again the problem
with the "7.0 TERM AND TERMINATION" section which effectively reduces
the rights to use all the subsequent version of EA TCKs to 3 + 5
5. Why doesn't the OCTLA V 3.0 automatically covers subsequent
versions of the TCK in the same, simple way it does for EA TCK
That would drastically simply the access to the TCKs in the presence
of a high cadence, six-month Java SE release cycle.
Thank you and best regards,
More information about the discuss