Support

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.

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.

At this stage the London Jamocha Community (LJC) has not been able to reach an agreement with Oracle to use the Java SE Technology Compatibility Kit (TCK) under the terms of the OpenJDK Community TCK License Agreement (OCTLA).

We will continue to work with Oracle on this matter.

All AdoptOpenJDK binaries are tested with our suite of functional, integration, and performance tests, including real workloads from popular libraries frameworks, languages 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.

OpenJDK 8

Where available, OpenJDK 8 binaries are supported on the minimum operating system levels shown in the following tables:

Key Value
HotSpot VM Hotspot VM
OpenJ9 VM OpenJ9 VM

Linux x64 ppc64le s390x aarch64
Centos 6.9 Hotspot VM OpenJ9 VM
Centos 7.4 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
Red Hat Enterprise Linux (RHEL) 6.9 Hotspot VM OpenJ9 VM
RHEL 7.4 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
SUSE Linux Enterprise Server (SLES) 12 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Ubuntu 16.04 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
Ubuntu 18.04 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM

Note: Any other Linux distributions that have a minimum glibc version 2.12 on x86 or version glibc version 2.17 on other architectures are expected to function without problems.

Windows x32 x64
Windows 7 SP1 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows 8 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows 8.1 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows 10 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows Server 2012 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows Server 2012 R2 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Windows Server 2016 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM

macOS x64
OSX 10.10+ Hotspot VM

AIX ppc64
AIX 7.1 TL4 Hotspot VM OpenJ9 VM
AIX 7.2 Hotspot VM OpenJ9 VM

OpenJDK 11

Where available, OpenJDK 11 binaries are supported on the minimum operating system levels shown in the following tables:

Key Value
HotSpot VM Hotspot VM
OpenJ9 VM OpenJ9 VM

Linux x64 ppc64le s390x aarch32 aarch64
Centos 6.9 Hotspot VM OpenJ9 VM
Centos 7.4 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
RHEL 6.9 Hotspot VM OpenJ9 VM
RHEL 7.4 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
SLES 12 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM
Ubuntu 16.04 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM
Ubuntu 18.04 Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM OpenJ9 VM Hotspot VM

Note: Any other Linux distributions that have a minimum glibc version 2.12 on x86 or version glibc version 2.17 on other architectures are expected to function without problems.

Windows x32 x64
Windows 7 SP1 Hotspot VM Hotspot VM OpenJ9 VM
Windows 8 Hotspot VM Hotspot VM OpenJ9 VM
Windows 8.1 Hotspot VM Hotspot VM OpenJ9 VM
Windows 10 Hotspot VM Hotspot VM OpenJ9 VM
Windows Server 2012 Hotspot VM Hotspot VM OpenJ9 VM
Windows Server 2012 R2 Hotspot VM Hotspot VM OpenJ9 VM
Windows Server 2016 Hotspot VM Hotspot VM OpenJ9 VM

macOS x64
OSX 10.10+ Hotspot VM OpenJ9 VM

AIX ppc64
AIX 7.1 TL4 OpenJ9 VM
AIX 7.2 OpenJ9 VM

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:

First Availability End of Availability [1]
Java 8 (LTS) March 2014 At Least Sep 2023 [2]
Java 9 Sept 2017 March 2018
Java 10 March 2018 Sept 2018
Java 11 (LTS) Sept 2018 At Least Sept 2022 [2]


Notes:
[1] As a general philosophy, AdoptOpenJDK will continue to build binaries for LTS releases as long as the corresponding upstream source is actively maintained.

[2] 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 VM.

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.

Mailing List 

Submit an Issue 

Ask on Slack