We and other EC members continue to be wonder why there is not a simple solution to the issue of inclusion of ASLv2 licensed software into Java platform JSRs. At the last Java EC face to face meeting, there was a reference to http://www.apache.org/licenses/GPL-compatibility.html, but no answers to basic followup questions.
We would like to understand why, in the Specification Lead's view, ASFv2 licensed software should not be included in Java platform JSRs under these revisions. We observe that the current GPLv2+classpath exception license used by the platforms seems to allow for the inclusion of such code. An explanation beyond referencing http://www.apache.org/licenses/GPL-compatibility.html would be appreciated. Oracle's position as copyright holder and ability to relicense the Java platform on commercial terms should be addressed in the answer.
Jira issue originally created by user starksm64:
We and other EC members continue to be wonder why there is not a simple solution to the issue of inclusion of ASLv2 licensed software into Java platform JSRs. At the last Java EC face to face meeting, there was a reference to http://www.apache.org/licenses/GPL-compatibility.html, but no answers to basic followup questions.
We would like to understand why, in the Specification Lead's view, ASFv2 licensed software should not be included in Java platform JSRs under these revisions. We observe that the current GPLv2+classpath exception license used by the platforms seems to allow for the inclusion of such code. An explanation beyond referencing http://www.apache.org/licenses/GPL-compatibility.html would be appreciated. Oracle's position as copyright holder and ability to relicense the Java platform on commercial terms should be addressed in the answer.