Java Is Still Free
With the changes to Oracle JDK distribution and support, there has been considerable uncertainty over the rights to use Oracle JDK vs Oracle OpenJDK builds vs OpenJDK builds from other providers. There are various ways to get free updates, and (new and existing) paid support models available from various vendors to consider. This document has a Shorter Version and a much Longer Version section with all of the detail.
Want to Comment?
You can still get the Oracle OpenJDK builds and OpenJDK by other providers for free under an open source license, and the Oracle JDK remains free in some circumstances. See the callout and the rest of the section for the nuances on this.
Java SE / OpenJDK / Oracle OpenJDK Builds / Oracle JDK
The OpenJDK community creates and maintains the (GPLv2+CE) open-source Reference Implementation (RI) of the Java SE Specification as governed by the Java Community Process (JCP) and defined through an umbrella Java Specification Request (JSR) for each feature release.
There are implementations (mostly OpenJDK based) of Java SE from various providers such as AdoptOpenJDK, Amazon, Azul, BellSoft, Eclipse, IBM, jClarity, Red Hat, Oracle, SAP, and others.
Oracle JDK 8 is going through the "End of Public Updates" process, which means the April 2019 update will restrict commercial use. However, since Java SE 9, Oracle is also providing Oracle OpenJDK builds which are free for commercial use (but only updated for 6 months). There are also free OpenJDK builds from other providers like AdoptOpenJDK, Amazon, Azul, BellSoft, IBM, jClarity, Red Hat, the Linux distros et al.
Going forward there are several options to get a JDK. We focus on Java SE 8 and Java SE 11 which is the first Long Term Support (LTS) release under the new release cadence.
Some people want to continue using Java SE 8 for various reasons.
I WANT $FREE AND FREE (AS IN USE) JAVA SE 8, WHAT DO I CHOOSE?
You have several options to choose from. Please read them carefully, especially as how Oracle JDK is managing releases and updates is changing from Java SE 11 onwards.
NOTE: Oracle provides two quarterly updates for its Oracle OpenJDK builds and then transition users to the next version, every six months (this includes LTS).
I WANT $FREE AND FREE (AS IN USE) JAVA SE 11+, WHAT DO I CHOOSE?
Oracle plans to provide full paid support for Oracle JDK 8 until at least 2025 and Oracle JDK 11 until at least 2026 (details). There is a wide range of paid support options for Java SE / OpenJDK 8 and 11 binaries from Azul, BellSoft, IBM, jClarity, Red Hat, and others.
This page is left blank to separate the Shorter Version from the Longer Version.
This section deliberately has a lot of detail as there are nuances that need to be clearly explained. Please do yourself and your colleagues a favor by setting aside some proper time to read this in full. You'll thank yourself for it, seriously.
We'd also like to thank Simon Ritter, Stephen Colebourne, Hendrik Ebbers, Donald Smith, Jonas Konrad and many others for their earlier posts and permission to reuse their material. Appendix I - Signatories, Thanks and References gives a full list of accreditation and folks who are signatories to this document.
Feedback is welcome! Use this link where you can make suggested edits and comments.
This document will be updated over time as new information comes to light or if there is a verified correction to some factual data. Please check back here for updates and/or follow our @Java_Champions Twitter handle.
17 Sept 2018 1000 UTC
Initial Public Release
29 Nov 2018 1951 UTC
01 Mar 2019 2127 UTC
Updates to reflect the current OpenJDK / Java ecosystem
06 Mar 2019 0955 UTC
Minor updates to Liberica
09 Mar 2019 1439 UTC
Minor updates to Red Hat OpenJDK
The following sheet is tracking known dissemination of this document. Please update if you share this doc!
Table of Contents
With the recent changes to Oracle JDK distribution and support, there has been considerable uncertainty over the future of Java, over the software lifecycles, and over vendor-provided support. This document summarizes the changes Oracle has made, and the options available for users of Java SE.
WHAT DO WE MEAN BY FREE?
In a nutshell, the word "free" has two distinct meanings in software:
As explained in the Shorter Version, you can still get Java SE binaries "free as in beer" from Oracle and other Java SE / OpenJDK providers (but check the update policies).
Although there are proprietary and/or restricted usage implementations of Java SE out there (Azul Zing, Oracle JDK etc), for a vast majority of users there is always the option of using an OpenJDK binary, which is "free as in speech" as it is GPLv2+CE licensed.
These changes have happened within a short time frame creating a perfect storm of uncertainty as day to day developers, who don't follow the industry news closely, get caught up. This leads to factually incorrect posts like:
Which are luckily counterbalanced by more accurate posts such as:
This article will cover the main areas of concern and what's being done about those concerns by the ecosystem. By the end of this post, you should be reassured that Java SE is still being well looked after and that it has a future stronger than ever!
Java SE now has a feature release every six months, using a new versioning scheme which was previously announced in 2017. Thanks to improvements in JCP processes, OpenJDK committers can now introduce spec changing features (such as var in Java SE 10) on the six-month cadence.
WHAT DOES LTS MEAN WITH REGARDS TO JAVA / OPENJDK?
Long Term Support (LTS) in OpenJDK is really just an understanding between the various contributors (led by Oracle and Red Hat) that the code line for Java SE 11 / 17 / 23 etc will be maintained for a longer period of time than six months.
Oracle will lead the first six months of an OpenJDK LTS code line, providing updates and producing Oracle OpenJDK builds, but will then afterward only provide updates for Oracle JDK, under a paid support plan.
However, Oracle will work with other OpenJDK vendors to hand over the OpenJDK LTS code line and allow them to continue working on it together to provide updates. Each vendor then has the choice of providing updates and/or paid support for the binaries they produce. This hand over has occurred for both Java SE 8 and Java SE 11 with Red Hat taking over those update projects.
NOTE: This does mean that in theory, Oracle's JDK could differ from the OpenJDK based binaries produced by other providers (this has always been the case). However, Red Hat and other project leaders have led the efforts to keep them in sync.
Understanding the new versioning scheme (including what LTS means) and how new features are introduced impacts how each version is maintained. By maintenance, we mean the provision of update releases with security patches and important bug fixes.
UPDATES vs SUPPORT
Updates refer to the code patches that have gone into OpenJDK and Oracle JDK. These have typically gone in for free until vendors decide that there's an End of Public Updates process.
Support means a commitment to fix bugs and it requires staff to answer users' problems, and that costs money. To be clear there has never been free support for Oracle JDK or OpenJDK.
Up to and including OpenJDK 8 / Oracle JDK 8, updates were provided by Oracle and other OpenJDK committers within a “feature release”. Feature releases, such as 8u91, 8u111 and 8u131 (on a six-month cadence) were superseded by each subsequent feature release. For example, once 8u111 was released, you would not get updates on 8u91.
Starting with OpenJDK 9 / Oracle JDK 9, the new six-monthly release cycle came into effect and updates now occur between "feature releases", i.e. Similar to 8u91 -> 8u111, once 12 is released, you will not get updates to 11 by Oracle (However, other OpenJDK committers, lead by Red Hat, will provide these).
Until Java 8, Oracle provided updates for the Oracle JDK for a 3+ year lifecycle, and usage was permitted in personal as well as commercial settings. The updates provided no support, and support required the purchase of explicit licenses from Oracle. Paid support also entailed longer update cycles.
Starting with Java 9, Oracle has moved to a faster cadence for Oracle JDK and also started producing Oracle OpenJDK builds. Updates will generally be provided for 6 months before they are stopped upon release of the next version. If updates/support are required for a longer duration, or for production use, then it must be purchased from Oracle (i.e. You must be on Oracle JDK). Periodically, releases will be marked “LTS”. These releases will be supported by Oracle through their standard support licenses for an extended period. As of right now, the Oracle update plan for Oracle OpenJDK builds, with updates, is as follows:
Oracle OpenJDK Build Version
At least through January 2020 (personal desktop use)
Ends January 2019 for commercial use
Superseded by Oracle OpenJDK build 10
Superseded by Oracle OpenJDK build 11 in Sept 2018
To be superseded by Oracle OpenJDK build 12 in March 2019 (this may be extended).
To be superseded by Oracle OpenJDK build 13
To be superseded by Oracle OpenJDK build 14
The idea here is simple. As has been the model of Java SE going way back to the Sun era, Oracle focuses on new innovations and moving Java SE forward. Organizations who wish to remain on legacy versions can do so via commercial support offerings. Of course, for some Java SE users and development shops, such rapid upgrade is not feasible.
The OpenJDK community works on a free, open-source implementation of the Java SE standard. Oracle contributes heavily to the project, and it is the basis for both Oracle OpenJDK builds and Oracle JDK. OpenJDK 11+ is interchangeable with Oracle JDK for applications that adhere to the Java SE standard. Oracle will continue to contribute to OpenJDK while they provide updates for the corresponding Oracle OpenJDK build version. Once that version is superseded, Oracle will cease contributing to that version and start updating the next one.
Oracle has been highly receptive to the idea of community maintenance (for OpenJDK 6 and 7) and will continue to support handover of OpenJDK to the community to a qualified volunteering entity once they have moved on to working on the next version. Red Hat stepped in to globally lead (and provide regular updates to) OpenJDK 6 and OpenJDK 7 projects after Oracle ended updates for them. After Red Hat stopped updating OpenJDK 6, Azul Systems stepped in to lead the project and they continue to provide updates to this day.
Red Hat is now leading OpenJDK 8 and OpenJDK 11. It is important to note that while Red Hat leads the OpenJDK 7, 8 and 11 projects, they are not the sole contributors! Other vendors provide patches and fixes as well. With OpenJDK 8, there will be more contribution than ever before from non-Red Hat companies, such as Amazon, Azul, BellSoft, IBM, jClarity, Google, SAP, and many others.
For consistency, the OpenJDK update cycle will be extended for the same versions that are deemed LTS for Oracle JDK. As of right now, OpenJDK support cycle is as follows:
NOTE: These times are subject to change and different providers all have slightly different timeline commitments. Therefore we use the term "At Least".
Supported primarily by Azul systems
At least through to June 2020 Supported primarily by Red Hat
At least through Sept 2023. Red Hat has led since Jan 2019 and will be supported by Amazon, Azul Systems, BellSoft, Google, IBM, jClarity, SAP, and others.
Superseded by OpenJDK 10
Superseded by OpenJDK 11 in Sept 2018
OpenJDK 11 (LTS)
At least through Sept 2025. Red Hat has led since Feb 2019 and will be supported by Amazon, Azul Systems, BellSoft, Google, IBM, jClarity, SAP, and others.
To be superseded by OpenJDK 13
To be superseded by OpenJDK 14
There are now a large number of Java SE / OpenJDK providers who provide either updates and/or paid support options. The following sections provide a lot of detail.
UPDATES vs SUPPORT
Updates refer to the code patches that have gone into OpenJDK and Oracle JDK. These have typically gone in for free until vendors decide that there's an End of Public Updates.
Support means a commitment to fix bugs and it requires staff to answer users' problems, and that costs money. To be clear there has never been free support for Oracle JDK or OpenJDK.
If you need a fix in a timely manner, someone to respond to your user requests, or if you want the reassurance that the binary you use is being backed by a vendor, then Azul, BellSoft, IBM, jClarity, Red Hat, Oracle et al. all offer choices.
A PHILOSOPHICAL POINT ON PAYING FOR OPEN SOURCE SOFTWARE
The industry at large has settled firmly on Open Source Software as the way forward. Because of its "Free as in speech" nature, OSS licenses allow folks to modify and adapt other people's software without fear of punitive action.
Many folks also enjoy the "Free as in beer" nature of much OSS software, but this comes at a great cost to the authors! Software developers, like anyone else, need to put a roof over their heads and food on their table. Vendors like Oracle pour vast amounts of money into Java SE (think 10s of $ Millions per year at the very least) and they do need to somehow pay for that cost.
So although you're certainly not obliged to go with a paid support option with one of the vendors, sometimes it's worth thinking about how you, the end users, can support the Java SE ecosystem to ensure it has a long lasting future!
Build from Source [OpenJDK, no commercial support, need to self-build]:
Until at least Sep 2023
Until at least Sep 2023
Major + Minor
Until at least June 2023
Major + Minor
BellSoft Liberica JDK
Until at least 2023
Until at least 2023
Major + Minor
Until Mar 2019
Oracle (via Oracle JDK)
* All Major = Linux x86, Mac OS X, Windows x64, Minor = various other platforms
Free Builds for Linux, Windows, Mac, etc. [OpenJDK, no commercial support]:
Amazon Corretto [OpenJDK base]:
Azul Systems [OpenJDK base]:
BellSoft [OpenJDK base]:
IBM [OpenJDK base + OpenJDK with Eclipse OpenJ9 VM]:
jClarity [OpenJDK base]:
Oracle JDK [OpenJDK base]:
Red Hat [OpenJDK base]:
The various Linux distros will continue to provide OpenJDK for their respective distributions including but not limited to Debian, Ubuntu, CentOS, Fedora, Mint, Alpine et al.
Please visit your distro homepage for more information.
AdoptOpenJDK is backed by Amazon, Azul, GoDaddy, IBM, jClarity, Pivotal, Red Hat and many more. It provides OpenJDK binary distributions (Hotspot and Eclipse OpenJ9 VMs) for a very wide range of platforms (Linux, Mac, Windows 32/64, Arm 32/64, z/OS, Solaris, AIX, PPC, s390 and more).
Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the OpenJDK. Corretto comes with long-term support that will include performance enhancements and security fixes. Amazon runs Corretto internally on thousands of production services and Corretto is certified as compatible with the Java SE standard. With Corretto, you can develop and run Java applications on popular operating systems, including Linux, Windows, and macOS.
Amazon offers long-term support for Corretto on AWS and includes performance enhancements and security updates for Corretto 8 until at least June 2023 at no cost. Updates are planned to be released at least quarterly. Corretto 11, corresponding to OpenJDK 11 is currently in preview and will be generally available during the first half of 2019. Amazon will provide LTS for Corretto 11 with quarterly updates until at least August 2024.
Azul provides OpenJDK binaries (Zulu) as well as a specialized Java platform (Zing).
Azul offers an option for all companies that do not want to skip all Java SE versions between LTS releases but cannot switch to the newest version every 6 months. Next, to the support for all LTS releases, where Azul provides 1 more year of support than Oracle, Azul offers support for so-called Medium Term Support (MTS) releases for their Zulu JDK. Here you can buy commercial support for every second Java SE version regardless of if it is LTS or not. The support duration of these versions is different. Azul tries to provide a good time range to prepare migration to the next version and defines 3 different durations for support of Java SE versions.
Unlike Oracle, the commercial support of Zulu is not defined per CPU but based on the number of systems. A system is defined as a physical or virtual server. The only difference between standard and premium is the availability of support. By buying premium support you can call Azul 24x7.
Liberica JDK is a supported OpenJDK based binary distribution for desktop, server or embedded use. Supported platforms: Linux x86 32 & 64 bit, Windows x86 32 & 64 bits, MacOS X, Linux ARM 32 & 64 bit, Solaris SPARC and x86. Additional platforms are available by request.
Liberica JDK has commercial support for LTS versions. The support pricing is calculated based on the number of desktops, physical or virtual servers or embedded platforms. Please contact firstname.lastname@example.org to get a quote.
IBM provides native JDK bundles for AIX, Linux (on x86, Power, zSystems), z/OS and IBM i. IBM offers the IBM SDK for Java SE versions for use with IBM products or platforms and for developer use from developerWorks. IBM also supports OpenJDK LTS binaries built and tested at AdoptOpenJDK.
For Java SE 7 and 8, IBM still provides security updates and bugfixes. The IBM support lifecycle will continue to be updated. Based on the new Java SE release schedule IBM has announced that the LTS releases will be available as OpenJDK with OpenJ9 binaries from AdoptOpenJDK.
The jClarity team consists of a number of well known Sun/Oracle Java Champions, Java User Group Leaders etc. jClarity co-founded AdoptOpenJDK and they currently lead the build team and hold the Chairperson and Director positions on the Technical Steering Committee. As well as commercial support for AdoptOpenJDK, users can also utilise their specialised performance analytics tools to ensure that migrations are smooth.
jClarity supports the AdoptOpenJDK OpenJDK binary distributions (Hotspot) for a very wide range of platforms (Linux, Mac, Windows 32/64, Arm 32/64, Solaris, AIX, PPC, s390 and more). See jClarity AdoptOpenJDK Support for details.
In June 2018, Oracle replaced its legacy “Java SE Advanced” perpetual license support product with a Subscription based offering that includes license and support. One of them targets Java SE on the desktop and the other one Java SE on the server, cloud, and Java SE in general. If you do not use Java SE on the desktop the “Java SE Subscription” will be the right support model for you. If you use Java SE on the desktop for client applications the “Java SE Desktop Subscription” product is available. If your software uses a Java SE server and Java SE based clients you can subscribe to both offerings.
Commercial support for Java SE applications on the desktop might become quite important for some companies since Oracle will drop several important desktop features from the JDK starting with Java SE version 11. If you are using Java SE on the desktop please read:
Red Hat produces OpenJDK binaries for various platforms that Red Hat Enterprise Linux runs on. Red Hat also provides its OpenJDK source RPMs for CentOS. Usually after 24h to 72h, the CentOS team has built binaries from it and has made these available for the CentOS distribution.
Red Hat won’t provide Java SE 9 and 10 releases. The next distribution that Red Hat plans to release is OpenJDK 11 for Red Hat Enterprise Linux 7. Currently, Java SE 8 is the supported release for Red Hat Enterprise Linux and the company will support it until 2023.
There are a number of changes with Desktop Java SE starting with Oracle JDK 11 that you need to be aware of.
Starting with Java SE 11, neither the OpenJDK builds or the Oracle JDK binaries include the JavaFX libraries. The JavaFX components will now be delivered as a separate SDK, or as artifacts that can be used via build tools (e.g. Apache Maven, Gradle et al.). As a positive consequence of this decoupling, JavaFX development can now have its own roadmap.
JavaFX is still being developed in OpenJFX, which is a project under the OpenJDK community umbrella. Oracle, other companies, and individuals in the wider community are actively developing JavaFX. An automatically synced GitHub mirror is created as well, lowering the barrier for developers to contribute code and issues to JavaFX.
At the moment builds for OpenJFX are only provided by Gluon but Azul, AdoptOpenJDK, and others also will bundle OpenJFX. As all the OpenJFX source code is 100% open, others can create or distribute binaries as well. At OpenJFX, a similar approach as the one in OpenJDK is followed, where after releasing JavaFX 11, the focus is on JavaFX 12 and so on.
Gluon provides a Support Plan for companies who want Long Term Support for JavaFX 11.
The javapackager, which allows bundling applications and its dependencies with (a subset of) the JVM is no longer part of OpenJFX and is removed from Oracle's JDK and Oracle OpenJDK builds starting with Java 11. A JEP has been submitted for adding a Java Packaging Tool to OpenJDK. While the new Java Packaging Tool will not be ready for the Java 11 release, Gluon is working on a tool allowing Java 11 applications to be packaged into native images.
If you are using Java Web Start technology to distribute desktop clients you should take care about the current situation since Oracle has removed Web Start from Java.
Q. Differences between OpenJDK vs Oracle OpenJDK builds vs Oracle JDK?
We'll just talk about Java 11+ LTS releases here. Oracle JDK and Oracle OpenJDK build are identical, but are licensed in different ways (commercial and GPLv2+CE respectively).
Oracle JDK / Oracle OpenJDK builds and OpenJDK builds from other providers will be built from the same source for the first six months of updates and should be interchangeable for that period. After six months Oracle JDK / Oracle OpenJDK builds will be built from Oracle's own fork. Other OpenJDK providers will continue to create binaries from the OpenJDK updates project. Oracle JDK / Oracle OpenJDK and OpenJDK build from the other providers may, therefore, differ in small ways. Binaries from various parties may, of course, vary over time.
Q. Differences between OpenJDK from (non-Oracle) provider A vs provider B?
We'll just talk about LTS releases here. As has been the case with the Java SE 6 and Java SE 7 updates projects, various providers work together upstream in the OpenJDK community, which provides the common repositories, mailing lists, and other infra to share the work. This means the difference between OpenJDK-based binaries are mostly non-core features, like extended monitoring and diagnostic support. Although there may be small differences in the final binaries (perhaps a provider-specific tool etc) they will all at least have the same security and stability baseline as has been true for many years.
Q. Differences between Red Hat OpenJDK and AdoptOpenJDK?
Andrew Haley (Java Platform Lead Engineer, Red Hat) stated: "...we tweak our builds to use system libraries rather than bundled libraries and we make a few other distro-specific patches. Also, as a matter of policy, our distros are built from source."
For a more detailed technical comparison of Red Hat OpenJDK (for Windows) and AdoptOpenJDK see Alex Kasko’s comment on Stack Overflow.
Q. If I stay on Oracle JDK 8 / 11, do I have to pay to get security and bug fixes?
For Oracle JDK 8, for personal desktop use, for development, testing, prototyping, demonstrating and with certain types of applications, then no. For most commercial use after the April 2019 update, then yes.
Q. If I stay on OpenJDK 8 / 11, do I have to pay to get security and bug fixes?
Not necessarily. As was the case with Java SE 6 and Java SE 7, Oracle works with the OpenJDK community to transition the leadership of OpenJDK update projects to other contributors. This has worked well for over a decade. Red Hat will continue this leadership in OpenJDK 8 and OpenJDK 11 with help from Oracle and other parties. This means important patches will get selectively backported. You then have the choice of taking downstream OpenJDK based binaries from a variety of providers for free, or as part of a paid support offering. There is an OpenJDK Vulnerability group which deals with 0-day exploits and CVE's and ensures that fixes get out as quickly as possible.
Q. Will Oracle’s JDK 8 and 11 still be available for download (last public release)? For example, a company has software that only runs on Oracle's JDK 8 and they provision a new machine after January 2019?
You can still download older versions of the Oracle JDK up to the point where the public updates stop. There is no reason to expect these archives to be removed. Moreover, Oracle JDK 8 continues to be free for personal desktop use, for development, testing, prototyping and demonstrating and with certain types of applications through at least 2020.
Q. If someone is using Oracle JDK 8 to run commercial software, after April 2019 do they need to purchase a license?
No. The user can continue to use Oracle JDK 8 indefinitely without paying. The only cost is if they want to get updates beyond April 2019, in which case they will need to purchase an "Oracle Java SE subscription". This follows the usual “End of Public Updates” process which has been in practice for well over a decade. Also, note that Oracle JDK 8 continues to be free for personal desktop use, for development, testing, prototyping and demonstrating and with certain types of applications through at least 2020.
Q. What happens to Oracle Java Web Start after April 2019? Does it continue to run or at what point do you need to purchase a license?
Since Web Start is part of Oracle JDK 8 it will continue to work and can be used indefinitely without cost. As above if you need updates (bug fix and security patches) you will need to purchase a "Java SE subscription". If your end users are consumers, they are covered for free until at least 2020. Oracle has stated that they will continue to support (i.e. provide commercial updates for) Java Web Start at least until March 2025. There is also IcedTea-Web as an alternative and Karakun is working on an OSS replacement for Web Start.
Special thanks go to the following folks who paved a road with their earlier blog posts. Much of the material in this document was collated (with permission) from these sources.
The following Java ecosystem folks back this document as a fair and balanced record of the state of Java SE / OpenJDK and plans for free updates and/or paid support.
AdoptOpenJDK co-lead, Java Champion, London JUG Leader, Member of JCP Executive Committee, Jakarta EE Steering Committee Member, CEO @ jClarity
Java Champion, JUG Dortmund Leader, JSR EG member, Co-founder of Karakun
Java Champion, Malmö JUG Leader, JCP Executive Committee Member, EE4J PMC Lead, Jakarta EE WG Member
Java Champion, The Java Specialists’ Newsletter, JCrete Founder
Ivan St. Ivanov
Java Champion, Bulgarian JUG Leader, jPrime Conference Organizer, Virtual JUG Leader, VIDA Software co-founder
Java Champion, Creator Joda and ThreeTen projects
Java Champion, Sevilla Java User Group Leader, JCP Executive Committee Member, Java Developer Advocate for JetBrains
Java Champion, Spring Developer Advocate for Pivotal, best-selling book author and prolific speaker worldwide
Java Champion, Oracle Developer Champion, co-founder Anderson Software Group, Inc.
Java Champion, JSR EG Member
Java Champion, JUG Leader, and Jfokus conference founder
Java Champion, JCP EC Member, Oracle Developer Champion, Hackergarten worldwide
Java Champion, author, podcaster, CTO of MacLaurin Group
Java Champion, Oracle Developer Champion, author
Java Champion, Spring Developer Advocate for Pivotal, conference speaker, & published author
Java Champion, jCrete cofounder, Performance tuning advocate, co-founder jClarity
Java Champion, Web Developer, and Developer Advocate at Okta. Classic VWs Enthusiast.
Java Champion, Montréal JUG & Devoxx4kids Québec leader, EasyMock and Objenesis lead developer, conference speaker
Java Champion, author of “Core Java”
Java Champion, Apache NetBeans Committer, Technical Author, Jakarta EE Consultant, and Instructor.
Java Champion, Apache NetBeans Committer, Jakarta EE Mojarra Committer, Technical Author, Podcaster
Java Champion, Dukes Choice Award winner, Microsoft Cloud Developer Advocate, Co-founder Gluon
Java Champion, former JCP EC Member, co-founder jClarity, author of “Java in a Nutshell” & “Optimizing Java”
Java Champion, Oracle Developer Champion, Gluon co-founder
Thor Henning Hetland
Java Champion, Principal at Capra Consulting. Community leader Cantara, javaBin, JavaZone, Oslo Software Architecture and more..
Java Champion, JUG Torino co-leader, Jetty team member
Java Champion, Author of Enterprise OSGi in Action
Java Champion, co-author of Continuous Delivery in Java, and leader within the LJC
Java Champion, Oracle Groundbreaker Ambassador, JCP member, EGJUG leader. International speaker, Author of "JavaFX essentials", "Getting started with clean code, Java SE 9", “Hands-On Java 10 Programming with JShell”, and “Secrets of the Java Champion” Won Duke’s choice 2014, 2015 awards, & JCP outstanding adopt-a-jar participant 2013 awards.
Java Champion, Oracle Developer Champion, Virtual JUG leader, Director of Developer Relations, Snyk.
Java Champion, Spring Data Project Lead at Pivotal Software, Inc.
Java Champion, author of “Développons en Java”
Java Champion, Creator of BlueJ and Greenfoot, author of ‘Objects First with Java’.
Java Champion, Director of OpsGenie Academy, Published Author, Speaker
Leonardo M R Lima
Java Champion, JSR Spec Lead
Java Champion, Senior Software Engineer at Tomitribe, Eclipse Foundation Committer, Guatemala Java User Group member, Speaker and board member of Latin America Virtual JUG JEspañol.
Java Champion, Chief Engineer, Leader of JavaZone, board member and former leader of javaBin – Norwegian Java User Group.
Java Champion, Senior Software Engineer at Netflix
Geir Magnusson Jr
Java Champion, Member Apache Software Foundation, CTO at fuboTV
Java Champion, JUG Leader JavaUP - Mexico - Speaker and member of JUG JEspañol.
Java Champion, JUG Leader of SouJava
Ian F. Darwin
Java Champion, Developer, Author, Trainer, Mentor, Speaker. Author of O’Reilly Java Cookbook, Android Cookbook, etc.
 See https://adoptopenjdk.net/quality.html