在Oracle(公司)的Java平台组任职产品管理经理的Donald Smith在去年宣称，公司计划在此后的几次发布内希望可以使得OpenJDK和Oracle JDK构建的二进制文件没有技术上的差别。我们现在是否处在这一步了呢？这两者之间没有技术上的差别了么？他在他新发表的博客上进行了表述。

在去年的Java One(译者注:“JavaOne 是每年一次的Java盛会，当然中国大陆现在也有了JavaChina，中国台湾有JavaTwo，而欧洲的JavaPolis则也是非常的壮观。 JavaOne是在Sun正式发布Java 1.0之后，Java这门新生的语言所拥有的自己的会议。”)盛会上，Mark Cavage宣称，Oracle将开放Oracle JDK的专有特征的源代码。就在此次盛会的前不久，在Oracle(公司)的Java平台组任职产品管理经理的Donald Smith在他发表的博客中说，公司计划“在此后的几次发布内希望可以使得OpenJDK和Oracle JDK构建的二进制文件没有技术上的差别”。

我们现在是否处在这一步了呢？如果你这样问Donald Smith，那么他会回答是的，但是“会有一些表面上的和打包方面上的差异”。

Oracle JDK构建 VS OpenJDK构建：目前的状况

It’s been one year since it was first announced that there should be little to no technical difference between OpenJDK builds and Oracle JDK binaries but this conversation shows no signs of stopping.

距离第一次宣称“OpenJDK构建和OracleJDK构建之间不应该有技术上的差异”已经有一年了，但是此次对话并没有显示这种差异不会继续存在的迹象。

In September 2017, we invited Uwe Schindler, Apache Lucene PMC Member and Contributor of the OpenJDK Project, to weigh in on the proposed changes. Here’s what he said:

2017年9月，我们邀请了Apache Lucene PMC成员和OpenJDK项目的贡献者——Uwe Schindler来发表对于被提议的改变的看法时，他说道：

The Java Core has been the same for OpenJDK Builds and Oracle Builds since Java 7, so you could easily change between versions starting from Java 7. At least when working in server environments. So yes, one could say “Java is open source” to that.

自从Java 7之后对于OracleJDK和OpenJDK构建而言，Java核心是相似的，所以从Java 7之后你可以很容易地进行两者之间的更换。至少在服务器环境中工作时是没有差异的，对此可以说“Java是开源的”

Still, there have been differences concerning the implementation of some components. Foremost that concerned GUI-environments (AWT/Swing) where some parts were omitted in OpenJDK (sound output, options for graphic editing).

此外，考虑到一些组件的实现还是有差异的。最重要的是在 OpenJDK 中 GUI 环境(AWT/Swing)的一部分是被忽略的(譬如：音频输出，图形编辑选项)
– Uwe Schindler

– Uwe Schindler

Read the full interview here.

在此处查看完整的访谈

One can, of course, choose to use Oracle JDK builds but since “Java is now developed as OpenJDK,” as Stephen Colebourne pointed out in a recent blog post, there are more choices out there.

但是自从“Java现在被发展为OpenJDK”人们当然能自己选择用Oracle JDK构建，正如Stephen Colebourne在他最近发表的一篇博客中指出的那样，其实还有很多选择。

A key point to grasp is that most JDK builds in the world are based on the open source OpenJDK project. The Oracle JDK is merely one of many builds that are based on the OpenJDK codebase. While it used to be the case that Oracle had additional extras in their JDK, as of Java 11 this is no longer the case.

需要抓住一个关键点就是在世界上大多数JDK构建都是基于OpenJDK项目的。Oracle JDK也仅仅是众多以OpenJDK代码为基础的构建之一。尽管在Oracle JDK中经常有额外的功能，但自从Java 11之后OpenJDK也有很多额外的功能了。

For the first 6 months of Java 11’s life, Oracle will be providing GPL+CE licensed $free zero-cost downloads at jdk.java.net with security patches. To get GPL+CE licensed $free zero-cost update releases of Java 11 after the first six months, you are likely to need to obtain them from a different URL and a different build team.
在Java 11发布之后的半年里，Oracle将会提供GPL+CE许可免费下载安全补丁在jdk.java.net。在Java 11发布半年后获取免费更新的GPL+CE许可，你可能就需要从不同的URL或者不同的构建团队获取了。
– Stephen Colebourne
– Stephen Colebourne

Read more about the costs involved here and here.

从这里和这里阅读更多关于花费的事

We will explore this topic in-depth at JAX London.

我们将在JAX London深度讨论这个话题。

RESOLVING TECHNICAL DEBTS IN SOFTWARE ARCHITECTURE
软件架构中解决技术上的债务
Dr. Carola Lilienthal (WPS - Workplace Solutions)
KEEPING UP WITH JAVA: LOOK AT ALL THESE NEW FEATURES!
跟上Java：看看这些全部的新特性！
Simon Ritter (Azul Systems)
CLOUD NATIVE COMMUNICATION: USING AMBASSADOR AND CONSUL CONNECT WITH JAVA APPS
云原生交流：使用AMBASSADOR和CONSUL来连接Java应用
Dr. Daniel Bryant (Big Picture Tech Ltd)

• JAX London Program »

Understanding the differences between Oracle JDK builds & OpenJDK builds

理解Oracle JDK和OpenJDK之间的一些差异

“BCL” license no more! Donald Smith explained in a recent blog post that JDK 11 will mark the beginning of a new era, one in which the tech giant offers “JDK releases under the open source GNU General Public License v2, with the Classpath Exception (GPLv2+CPE), and under a commercial license for those using the Oracle JDK as part of an Oracle product or service, or who do not wish to use open source software.”
不再是“BCL(binary code license)” 许可！Donald Smith在他最近发表的博客上解释道，JDK 11意味着一个新的纪元的开始，由巨头公司提供的“在GPLv2+CE的开源许可下的jdk发布，以及为了那些使用作为Oracle的一部分的产品和和服务的OracleJDK，或者不希望使用开源软件的那些人提供商业许可”。

Different builds will be provided for each license, but these builds are functionally identical aside from some cosmetic and packaging differences.
针对每个许可都会有构建差异，但是除了表面上的和打包上的差异，这些构建在功能上是一致的。
– Donald Smith
– Donald Smith

From Java 11 -which will be released on September 25– forward, Oracle JDK builds and OpenJDK builds will be essentially identical, he added. However, there will be some “cosmetic and packaging differences.”

他补充道：从将在9/25发布的Java 11开始，Oracle JDK和OpenJDK构建将没有本质上的区别。然后两者还是有一些表面上的和打包上的差异。

Here are the changes, as explained by Donald Smith:

正如Donald Smith所解释的，有如下改变：

• Oracle JDK 11 emits a warning when using the -XX:+UnlockCommercialFeatures option, whereas in OpenJDK builds this option results in an error. This option was never part of OpenJDK and it would not make sense to add it now since there are no commercial features in OpenJDK. This difference remains in order to make it easier for users of Oracle JDK 10 and earlier releases to migrate to Oracle JDK 11 and later.

• 当时用 -XX:+UnlockCommercialFeatures 参数时Oracle JDK 11会发出警告，然而在OpenJDK构建时此选项会导致一个错误。这个参数不是OpenJDK的一部分并且自从OpenJDK没有商业特性加上这个选项并没有什么意义。这个差异的存在是为了使用Oracle JDK 10及以前的版本的用户更容易切换到Oracle JDK 11及以后的版本。

• Oracle JDK 11 can be configured to provide usage log data to the “Advanced Management Console” tool, which is a separate commercial Oracle product. We will work with other OpenJDK contributors to discuss how such usage data may be useful in OpenJDK in future releases, if at all. This difference remains primarily to provide a consistent experience to Oracle customers until such decisions are made.
• 通过配置Oracle JDK 11可以通过“高级管理控制台”工具提供可用的日志数据，这个工具是Oracle商业产品的一个分支。如果可以的话，我们将和OpenJDK的贡献者一起讨论如何使这样的可用数据可以在未来发布的版本中变得有用。直到讨论出结论之前，这个差异的存在主要是为了Oracle客户提供一个持续的体验。
• The javac –release command behaves differently for the Java 9 and Java 10 targets, since in those releases the Oracle JDK contained some additional modules that were not part of corresponding OpenJDK releases:
• 自从那些发布版本后，Oracle JDK含有一些在与之对应的OpenJD K中没有的附加模块，也就是说javac命令的使用与java9和java10有区别。
  • javafx.base
  • javafx.controls
  • javafx.fxml
  • javafx.graphics
  • javafx.media
  • javafx.web
  • java.jnlp
  • jdk.jfr
  • jdk.management.cmm
  • jdk.management.jfr
  • jdk.management.resource
  • jdk.packager.services
  • jdk.snmp

This difference remains in order to provide a consistent experience for specific kinds of legacy use. These modules are either now available separately as part of OpenJFX, are now in both OpenJDK and the Oracle JDK because they were commercial features which Oracle contributed to OpenJDK (e.g., Flight Recorder), or were removed from Oracle JDK 11 (e.g., JNLP).

这个差异的存在是为了一些特殊的遗留用法提供连续性的体验。上述模块作为OpenJFX的部分现在既可以单独使用，也能在OpenJDK和Oracle JDK上使用。因为这些是Oracle贡献给OpenJDK(也就是Flight Recorder)的或者从Oracle JDK 11(也就是JNLP)中被移除的商业特性。

• The output of the java –version and java -fullversion commands will distinguish Oracle JDK builds from OpenJDK builds, so that support teams can diagnose any issues that may exist. Specifically, running java –version with an Oracle JDK 11 build results in:

• java -version和java -fullversion命令的输出将用于区别Oracle JDK构建和OpenJDK构建，这样支持团队就能诊断任何可能存在的问题。尤其用Oracle JDK11构建时运行java -version会输出：

java 11 2018-09-25

Java(TM) SE Runtime Environment 18.9 (build 11+28)

Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)

And for an OpenJDK 11 build:

对于OpenJDK11构建，运行java -fullversion将会输出：

openjdk version “11” 2018-09-25

OpenJDK Runtime Environment 18.9 (build 11+28)

OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

• The Oracle JDK has always required third party cryptographic providers to be signed by a known certificate. The cryptography framework in OpenJDK has an open cryptographic interface, meaning it does not restrict which providers can be used. Oracle JDK 11 will continue to require a valid signature, and Oracle OpenJDK builds will continue to allow the use of either a valid signature or unsigned third party crypto provider.
• OracleJDK一直以来都需要第三方的加密提供者通过一个已知的证书做签发。而OpenJDK里的加密框架一直都开放了一个加密接口，这意味着OpenJDK并不被需要被使用的加密提供者所限制。Oracle JDK 11将继续需要一个有效签名，Oracle OpenJDK构建将继续允许使用一个有效的签名或者一个没有签名的第三方加密提供者。
• Oracle JDK 11 will continue to include installers, branding and JRE packaging for an experience consistent with legacy desktop uses.
• Oracle JDK 11为了桌面上的遗留用法和用户体验保持一致将继续包括安装组件，品牌推广和JRE打包

Oracle OpenJDK builds are currently available as zip and tar.gz files, while alternative distribution formats are being considered.

Oracle OpenJDK构建目前针对zip和tar.gz文件可用，与此同时许多可替换的格式也在被考虑进去。