Lastly, we would like the community to stay involved with the process of having the latest JDKs available on SDKMAN. That means that we are forced to keep serving the Zulu JDK as default until ships a JDK 8 variant (or we make JDK 9 or 10 the new default, whichever comes first). This is where things get a bit more interesting: does not provide an OpenJDK distribution for any version of Java less than 9.0.

Since SDKMAN is all about convenience for it’s users as opposed to driving forth the ideology of vendors, we have chosen JDK 8 as our sensible default for the forseeable future. With this in mind, we set up a Twitter poll to determine which OpenJDK distributions would be supported in the near future. SDKMAN is an Open Source initiative and we value the input of community members greatly. The time has now come to whittle down the OpenJDK variants that we distribute, focusing on one or two that are suitable for everyday development and production deployment.Īs with all such decisions, we like to involve our community in the direction we are moving. Up to this point, we have been adding various flavours of JDK under the java candidate, and this has caused confusion and sometimes even discord among community members. With such a broad array of new OpenJDK options, it’s time to take stock of what we currently have on SDKMAN and consolidate what we choose to support in the future. Last but not least, we’ve seen the appearance of “official” OpenJDK binaries for all major platforms on the Oracle-backed portal. We’ve seen the introduction of a rapid six month release cadence, the emergence of a new JDK distribution called AdoptOpenJDK, as well as a rise in popularity of third party OpenJDK distributions such as the Azul Zulu JDK.

It’s been little over a year since we started serving JDKs on SDKMAN and much has happened in the Java world since.

Open jdk version