As Mark Reinhold, Chief Architect for Java SE at Oracle, pointed out on Twitter [0], that patch was meant for Oracle's product VM, a minor fork of OpenJDK, which has
"commercial features" just like other vendors' VMs. Since it was checked into OpenJDK by mistake, it has been backed out of OpenJDK again within 24 hours[1].
Some of the key points of Oracle's Java SE strategy[2] are:
* Oracle plans to contribute the results of the combined Oracle Java HotSpot and Oracle JRockit JVMs to the OpenJDK project.
* The Oracle JDK and Java Runtime Environment (JRE) will continue to be available as free downloads, with no changes to the existing licensing models.
If you'd like to learn more about it and the ongoing JVM convergence work, I'd recommend reading Henrik Ståhl's blog post from last year here:
Some of the key points of Oracle's Java SE strategy[2] are:
* Oracle plans to contribute the results of the combined Oracle Java HotSpot and Oracle JRockit JVMs to the OpenJDK project.
* The Oracle JDK and Java Runtime Environment (JRE) will continue to be available as free downloads, with no changes to the existing licensing models.
If you'd like to learn more about it and the ongoing JVM convergence work, I'd recommend reading Henrik Ståhl's blog post from last year here:
http://blogs.oracle.com/henrik/entry/oracles_jvm_strategy
- Henrik is Senior Director of Java Product Management at Oracle and runs a group responsible for product strategy for Java SE, among other things.
Dalibor Topic, Java F/OSS Ambassador, Java Product Group @ Oracle
[0] https://twitter.com/#!/mreinhold/status/142122264220008448
[1] https://twitter.com/#!/mreinhold/status/142102137130844161
[2] http://www.oracle.com/us/corporate/press/173782