|JCP approves Java 7 and 8 road maps|
|Tuesday, 07 December 2010|
The votes are in for Oracle's proposed roadmap for Java 7 and 8 - and Oracle's plans have been accepted. This leaves Apache having to decide whether to quit the JCP as it threatened last month.
After an extension to the original deadline the members of Java's governing body, the JCP, have voted to approve the proposals for Java SE 7 and Java SE 8. This poll that had acquired added significance as a result of the Apache Software Foundation's request to fellow JCP members to vote against Oracle's plans as a protester over the fact that Project Harmony has not been granted a TCK licence.
After Apache issued its ultimatum to Oracle, Oracle responded with an official response that stated:
We would encourage Apache to reconsider their position and work together with Oracle and the community at large to collectively move Java forward. Oracle provides TCK licenses under fair, reasonable, and non-discriminatory terms consistent with its obligations under the JSPA.
What Apache intends to do next is currently unclear but what has emerged is that while voting against Oracle Apache and Google (whose Andriod operating system uses a subset of Harmony) their no votes were qualified by an explanation that the decision was not based on the technical merits of Oracle's plan. but rather as an objection to field-of-use and licensing restrictions imposed by Oracle.
Equally, some of those voting "yes" to Java 7 and 8, including IBM, SAP AG, Eclipse and Credit Suisse, indicated their support of Apache and Google by saying their votes were based on the technical merits of the Oracle roadmap but that they objected to the field of use and license restrictions imposed by Oracle.
We now have to wait and see if Apache follows through and leaves the JCP. Some commentators have pointed out that the chances of Apache gaining a licence to use the TCK were always slim and they could side step the issue by simply pointing out that Harmony is a good open source implementation that is available now and that proof of compatibility via an imperfect test suite (all validation suites are imperfect) is unnecessary.
Related news items:
|Last Updated ( Tuesday, 07 December 2010 )|