Insights and updates on Java SE and OpenJDK from the Java Platform Group Product Management Team

  • October 15, 2018

The OpenJDK Community TCK License Agreement (OCTLA)

Donald Smith
Sr. Director of Product Management

After launching the OpenJDK Community as the place to collaborate on open source implementations of the Java SE Platform back in 2006, the next logical step was to make the Java SE TCK (JCK) available to those working in and contributing to OpenJDK.  Sun Microsystems did this via the “OpenJDK Community TCK License Agreement” (OCTLA), made available in 2007 with certified builds appearing in 2008.  Oracle continued and expanded on this program by releasing an OCTLA for Java SE 7, another for Java SE 8 and, given the new release cadence, a single agreement for Java SE 9 and later.  There have been dozens of signatories across these Java SE versions. 

The initial OCTLA FAQ is still available here.  Oracle has continued to apply the traditions and intent of the OCTLA program as it was originally conceived.  That is, the OCTLA is for individuals and organizations who are working in and contributing to the OpenJDK Community, with OCTLA tested implementations from such individuals and organizations distributed only under the GPL license of the OpenJDK code.  As noted in the FAQ, the OCTLA is not for “independent implementations of Java technology standards.”  For independent implementations Oracle offers commercial JCK options, which helps to fund the overall development of Java.  Indeed, many of the OCTLA signatories who participate in the OpenJDK Community also have commercial JCK agreements for their independent implementation (non-OpenJDK) based products and services.  Some examples of independent implementations of Java technology standards over time include BEA JRockit and IBM J9

Oracle has consistently enforced the spirit and intent of this longstanding program for the benefit of the OpenJDK Community, and plans to continue the program as it has since the acquisition of Sun.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.