This page shows previous versions of the Eclipse Adoptium Interim Build Labeling Requirements. These requirements are no longer in effect.
Please see Eclipse Adoptium governance page for the current requirements.
Eclipse Adoptium Interim Build Labeling Requirements v 1.0:
The Eclipse Adoptium project may make available for testing, but not market or promote for extended or production use, binary builds created as a development step towards what is intended to be a Java SE implementation passing the Java SE TCK licensed to the Eclipse Adoptium project by Oracle that in each case (a) otherwise complies with the Eclipse Adoptium project charter, (b) excepting portions from OpenJDK, is developed primarily within the Eclipse Adoptium project, and (c) does not include any content from the OpenJ9 Project or Oracle’s GraalVM project(s) or any successors of either of the foregoing, except to the extent present in any future version of the Java SE reference implementation from Oracle (“Intermediate Builds”) subject to the following conditions:
i. such Intermediate Build is marked with the word "UNTESTED" or "INCOMPATIBLE" or "UNSTABLE" or "BETA";
ii. the Eclipse Adoptium project displays the following notice in such a manner that anyone downloading the Intermediate Build must see the notice before commencing the download (substituting in the relevant link where noted):
"This is an intermediate build made available for testing purposes only. The code is untested and presumed incompatible with the Java SE specification. You should not deploy or write to this code, but instead use the tested and certified Java SE compatible version of the code that is available at [include a url and a link]. Redistribution of any Intermediate Build must retain this notice."
The Eclipse Adoptium project must also include the same notice as a README.JAVASE file with any source code bundle (e.g. tarball) download that corresponds to the Intermediate Build;
iii. the Eclipse Adoptium project shall not distribute (except as a passive download as provided above), market or promote Intermediate Builds, including without limitation in connection with providing any goods or services.
iv. excepting mirror repositories of unmodified source code directly obtained from OpenJDK, the Eclipse Adoptium project must include the following README.JAVASE file in the root directory of any source code that is used in an Intermediate Build and that it may make available through access to a revision control system (e.g. git) (substituting in the relevant Project name and link where noted):
“This version of [Project name] source code is made available in support of the open source development process. Some numbered or tagged revisions of this source may have been tested and found to pass the Java SE TCK, and you can find information on which revisions or tags at [include URL and link]. Please note that since only binaries can be tested, source code cannot be described as a compatible implementation of the Java SE Specification. The different build environment on your machine and any changes you may make to this code could render your resulting build incompatible. Because of this, writing or deploying applications to builds based on this code can lead to lack of portability. You should instead consider deploying production applications on the pre-built binaries of [Project Name] that are available at [include a url and a link] that have been tested and certified to meet the Java SE compatibility requirements."
v. any mirror repository of unmodified source code directly obtained from OpenJDK that is used in an Intermediate Build that is made available through access to a revision control system (e.g. git) must include the following in a public facing description of such source code:
"This source code is an unmodified mirror of source code obtained from OpenJDK [include a url and a link]. It has been and may still be used to create builds that are untested and incompatible with the Java SE specification. You should not deploy or write to this code, but instead use the tested and certified Java SE compatible version of the code that is available at [include a url and a link].”