AdoptOpenJDK builds and tests binaries for different source code streams based upon OpenJDK. Our binaries undergo extensive testing,
and are made available with two distinct quality levels - release and nightly.
Releases have passed all the available OpenJDK test suites and our additional tests (donated by the community), ensuring the best
quality binary available. We recommend you choose releases for running your applications. Furthermore, releases that have passed
the Java Compatibility Kit (JCK) test suites are denoted by a blue shield containing a check mark in their download button.
We recommend you choose these releases for running your applications.
Nightly builds have passed basic quality level testing. The nightlies may include functionality and implementations that are unstable, or have not had the benefit of long running tests. Use these nightlies if you wish to check
the very latest capabilities and fixes, and to see what is coming in the next release.
The London Jamocha Community (LJC) have an agreement with Oracle to use the Java SE Technology Compatibility Kit (TCK) under the terms of the OpenJDK
Community TCK License Agreement (OCTLA).
Oracle has requested that the LJC stop TCK testing OpenJDK with Eclipse OpenJ9 binaries, and remove specification compatibility marks from
the existing OpenJDK with Eclipse OpenJ9 binaries available at AdoptOpenJDK. The LJC is working with Oracle to reach an agreed interpretation
of the OCTLA, and in the meantime have agreed to stop using the TCK for OpenJDK with Eclipse OpenJ9 and will remove the existing compatibility marks.
AdoptOpenJDK will continue to run the TCK for Hotspot based OpenJDK binaries at AdoptOpenJDK.
All AdoptOpenJDK binaries are tested with our suite of functional, integration, and performance tests, including real workloads from popular libraries
and applications. We remain confident in the quality of our builds.
Read Java Is Still Free for some background information. We are prepared to stand behind our release quality binaries, so each build that is identified as a "Release" receives support via the AdoptOpenJDK community. Our support means that you can raise an issue to describe a bug you have found in the build,
and we will work with you and the appropriate development team to resolve it. Any fixes we identify will be delivered as part of the next AdoptOpenJDK release.
The frequency of AdoptOpenJDK releases is guided by the schedule of our dependencies. We produce builds based upon source code at OpenJDK, Eclipse OpenJ9, and SAP Machine.
OpenJDK provides a new feature release every six months, and a maintenance/security update based upon each active release every three months. We will follow this schedule for publishing binary releases from AdoptOpenJDK to ensure you get the latest,
most secure builds.
In addition, every three years one feature release will be designated as the Long Term Supported (LTS) release. We will produce LTS releases for at least four years. This assurance will allow you to stay on a well-defined code stream, and give
you time to migrate to the next, new, stable, LTS release when it becomes available.
Based upon this roadmap, and starting with Java 8:
||End of Availability 
|Java 8 (LTS)
||At Least Sep 2023 
|Java 11 (LTS)
||At Least Sept 2022 
 As a general philosophy, AdoptOpenJDK will continue to build binaries for LTS releases as long as the corresponding upstream source is actively maintained.
 We fully expect that OpenJDK8 will have open community maintainers beyond January 2019, so we expect to be able to continue supporting JDK8 beyond that date. Until maintainers have been established we are unable to make a definitive statement. This position is the same for JDK11 and all future "LTS" releases.
The Eclipse OpenJ9 Support Document covers extra support info for that variant.
As a community of open source developers, our commitment is to triage any issues raised and champion them in the appropriate source code project. Of course, if the problem arises from the way we build and test the code we can fix that directly -- but
other bugs will be fixed on a "best effort" basis by the correct source project community. If you are looking for higher levels of assurance you should contact commercial companies offering support on these binaries.
We welcome feedback on any aspect of the project.