That’s the developer story Google is pitching in any case, but there’s a massive legal narrative here that can’t be forgotten. As such, Google wants to put more resources into OpenJDK where the team can have a bigger impact on new features and improvements. When we asked Google why now, the company pointed to to the release of Java 8 last year and the introduction of new language features such as lambdas.

That may be true, but if that was the only reason Google made the complete switch to OpenJDK, the company would have done so years ago. Google is hoping that Android developers will appreciate the change because it simplifies the code on which they build apps - a common codebase for these Java API libraries, as opposed to multiple codebases. Google has committed several hundreds of changes to the open-source repository in relation to adopting OpenJDK. Use openjdk classes from package.Ĭopy all files from jdk/src/share/classes and jdk/src/solaris/classes directories in openjdk into libcore/ojluni/src/main/java.Ĭopy following native files from openjdk to libcore/ojluni/src/main/native: The code commit in question, which shows 8902 files were changed, clearly notes OpenJDK code was added to Android:Ĭreate new libcore/ojluni directory with src/main/java and src/main/native subdirectiories. Google’s decision to “consolidate” its efforts with OpenJDK means it is moving away from its own implementing code to Oracle’s open-source code.

Oracle, which develops Java, has two implementations of these libraries: the proprietary JDK version and the open source OpenJDK version.

Android provides certain Java API libraries to support the development of apps in the Java programming language, broken into two parts: the APIs to the libraries, and the implementing code developed by Google that make said libraries work.

Oracle open jdk