Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Tim Webb
Vice President of Operations and a passionate technologist who thrives on merging software and marketing. Follow @timrwebb for periodic musing. A developer by birth, an optimizer by necessity, a forever believer in the ability of software to improve what you do.
Posted on Jan 15th 2019

There is a lot of concern regarding Oracle JDK in Enterprises, in particular with the new licensing model that is now in effect. If you are immediately required to discontinue use of all Oracle JDKs, scroll to the end for steps to facilitate that change. If you can wait just a little bit, it’s important to clarify a few key points. For context, you can get a summary of key information about the change from https://www.azul.com/eliminating-java-update-confusion/.

Points to Consider

  • Existing versions of MyEclipse ship with Oracle JDK, versions prior to JDK 11. In short, these versions are not directly impacted by this change.
  • The change to licensing for older Oracle JDK versions impacts the access to security updates, not the ability to continue to use MyEclipse with the bundled version of the JDK.
  • Future MyEclipse releases will be based on Open JDK version 11, or later.
  • We understand that some companies are being safe by fully restricting the usage of Oracle’s JDK in general, regardless of version, and have provided steps below to switch to Open JDK immediately, if required.
  • Our target timeline for the next MyEclipse release is in February 2019.

Using MyEclipse with OpenJDK

As mentioned above, if your company is requiring a move off of Oracle JDK, you have two options, as outlined in our forum.

Read Instructions Here