Oracle JDK 8 End of Public Updates: Business as Usual
By Jim Connors 15 January 2019

January 15, 2019 marks the final public update for the Oracle Java SE 8 release.  Henceforth referred to as Oracle JDK 8 (to avoid any confusion with Open JDK 8), this update culminates approximately 5 years of free commercial use and support under the terms of the Oracle Binary Code License Agreement.  Speaking from countless interactions, there is a fair amount of customer confusion and uncertainty concerning the fate of Oracle JDK 8 and Java going forward.  I hope these next few paragraphs provide some clarity.

There are two important facts regarding Java releases:


Referencing the figure above, let's look at the trajectory of the JDK 7 release to get a better understanding.  Introduced in July 2011, JDK 7 had a public lifetime just under 4 years.  The last public update (7u80) was released in April 2015.  Since that time, Oracle has continued patching JDK 7, fixing all known critical vulnerabilities and making those updates available to its commercial customers.  As of this article's publish date, the current JDK 7 update is 7u211, and it cumulatively patches a total of 182 security vulnerabilities since the time of the last public update.  The public versions of the Oracle JDK are, and will continue to be, free to download use, however, as time passes, those aging public releases will without question become increasingly exposed.  The question becomes whether organizations are willing to assume that risk.

Starting with JDK9, based on feedback from the community, Oracle has accelerated the Java release cadence to every 6 months.  Each of these 6 month releases will be freely available, supported and updated for 6 months and only six months.  Customers who wish to stay on releases longer than 6 months with updates and support have that option via the Java SE Subscription program.

In conclusion, current Oracle JDK customers have options -- three to speak of -- with regards to Java going forward, two of which entail no commercial obligation to Oracle or any other organization:

  1. You can continue to use the current publicly available releases as you do now indefinitely.  Oracle maintains an archive of old Java downloads that enables you to get at these releases at any time.  The one concern here is, over time, these releases will be increasing exposed to known security vulnerabilities.  If you are willing to assume that risk, then you're all set.
  2. If you are concerned about maintaining the latest security baseline, you can opt to follow the new 6 month Java release cadence.  These 6 month releases are updated twice during their lifetime with the latest security patches and are free to use under the GPLv2 with the Classpath Exception License.
  3. There are a whole host of good reasons why; if your organization would find it difficult if not impossible to move at the rapid 6 month cadence, you have the option of staying on of Oracle's designated Long Term Support (LTS) releases, and migrating to subsequent LTS releases at your pace.  These LTS releases are supported and updated with the latest security patches for 8 years and are available to customers via the Java SE Subscription program.