This follows months of speculation from developers, after odd bits of code from OpenJDK were spotted on Android updates. Google still hasn’t given a date for the Android N launch, so this gives developers a few months to read up on the differences between Java and OpenJDK.
On the user end, nothing will change. Most of the APIs and important systems are covered on OpenJDK, but it will mean a new standard for developers.
“Google has long worked with and contributed to the OpenJDK community, and we look forward to making even more contributions to the OpenJDK project in the future,” said Google in a statement to Venturebeat.
Oracle filed a copyright lawsuit against Google in 2010 for the use of 37 Java APIs. A federal district court originally ruled in favor of Google, but last year a U.S. Court of Appeals reversed, and ruled in favor of Oracle.
Moving to OpenJDK might therefor be a damage control move, to ensure Oracle cannot ask for more in the settlement. The U.S. Supreme Court has declined to hear Google’s further appeal.
Oracle has not commented on Google’s decision to switch to OpenJDK.
We don’t know all of what is going on behind the scenes, so all of the reasons behind the move are pure speculation for the moment. For all we know, this might have been the plan even before Oracle won the court case, and Google is just coming round to implementing it.
Editors' Recommendations
- From Android 1.0 to Android 10, here’s how Google’s OS evolved over a decade
- How to switch from Android to iPhone: A complete guide
- How to get Android apps on a Chromebook
- How to switch from iPhone to Android: The ultimate guide
- Chinese phone makers are challenging the Play Store. Should Google be worried?
