Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Java 11 recommendations


I agree that the Oracle JDK can be freely used for development and testing.

But I see a concern wrt the unusual wording “or your application” that subsequent use in an application is then infected imposing the commercial license on our users.

I'm not the EF or a lawyer, so I look to the EF and its lawyers to guide us. Yes OpenJDK is used on Jenkins; no problem. But what if I use Oracle JDK on my development machine? Does that infect Eclipse OCL, Papyrus, the Modeling EPP or SimRel. If I use Oracle JDK to develop a patch for SWT does that infect SWT?


Ed Willink

On 11/12/2018 20:52, Michael Keppler wrote:
Am 11.12.2018 um 21:10 schrieb Ed Willink:
Is there an EF policy on what Java 11 should be used?

I'm not the EF, and I'm not a lawyer.

It's a bit long, but worth reading, where the legal stuff is explained, and a huge number of alternatives are listed with pros and cons.

Oracle itself recommends switching to OpenJDK builds (which are available from multiple parties), as long as you need no commercial support. In fact, you can get an Oracle OpenJDK build, which is almost identical with the previous OracleJDK:

The change has been announced long ago, and basically it boils down to: You can use OracleJDK without a license for development, testing, etc. but for commercial deployment you need a license, or you need to use a different JVM build.

Ciao, Michael

PS: Doug, for me the AdoptOpenJDK Windows build generally worked fine, but its certificate store did not work at all, which was a killer for me.

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

This email has been checked for viruses by Avast antivirus software.

Back to the top