A few days ago, it became known by means of a message sent to the OpenJDK community distribution list, in which Bruno Borges from Microsoft's Java Product Management Division, announced that Microsoft has formally signed a collaboration agreement with Oracle "Oracle Contributor Agreement" and has been welcomed in the Java community.
With which in a first stage, the Microsoft Java development team are intended to be limited to correcting bugs and doing backport work to join the community and adapt to the OpenJDK development rules. The Java Engineering Team of Microsoft already affirmed that it is engaged with other groups and branches of Microsoft that use Java, along with partners in the Java ecosystem, including Oracle, Azul Systems, Red Hat, Pivotal, Intel, and SAP.
For example, Microsoft has already realized that in the OpenJDK community, the preferred way to promote innovation is to initially discuss changes before patches are released.
Then reaffirmed Microsoft's commitment to Java and that the team hopes to give something back to the Java community. Not only will the team break in with a heavy hand, though, they'll start off with little bug fixes and the like. so they can learn to be "good citizens within the OpenJDK community."
And is that it's been a long time since Microsoft worked hand in hand with Oracle to participate in Java development to ensure that the JVM provides adequate performance on your Windows operating system.
For previously, Microsoft's adoption of Java has come a long way since the 1990s, when Java creator Sun Microsystems sued Microsoft for a breach of contract.
Sun alleged that Microsoft had distributed a version of Java that was incompatible with Sun's, which threw a wrench into Sun's promise "Write Once, Run Anywhere" for Java. Microsoft responded, and the dispute was resolved in early 2001.
For the past few years, Microsoft has been launching massive recruiting campaigns where the main The goal was to attract former Oracle employees to strengthen their tool development teams. This has led to the standardization of Java development kits that allow Java developers to interact with their services on their Azure Cloud platform.
But nevertheless this is the first time that the giant integrates OpenJDK within its tasks to contribute directly to Java development. Borges himself is a former Oracle developer. He introduced Martijn Verburg as the leader of the Java engineering team that will work alongside other partners in the Java ecosystem.
Martijn Verburg is also CEO of jClarity, a leading contributor to AdoptOpenJDK acquired by Microsoft in August this year to enhance Java support on Azure. So it will presumably stay true to form and continue to contribute to the Java world, only now with Microsoft in its ranks.
This implementation is cataloged within the GNU GPL license with an exception of links, so some of the components of the Java class folders and websites are finalized from the license terms in order to be considered within the version stipulated as GNU.
Bruno Borges indicates that, at the beginning, Backports while continuing to study and observe the uses and policies that run on OpenJDK, for example, discuss on the mailing list to reach a consensus before looking to publish a patch.
You can read the original message In the following link.