I think, there could be existing a unique Java-license
There are some comments like at
where people say, that every license decision would make problems.
Either the Apache Harmony people or the GNU Classpath people would be unhappy with the license, Sun would choose.
But I don't think so.
For this, I want to go back in the history of OpenSource Java.
In November 2000 GNU Classpath have published it first version of GNU Classpath
It have had a much more liberal license then Kaffe, which only was licensed under GPL.
Later GNU Classpath has also makes its license much more liberal. Under the GPL with linking exception. This means, it is alowed to compile and link the GNU Classpath files against other files of any other license.
A little bit more later, Kaffe ported GNU Classpath to its platform. So there existing different OpenSource JVMs, but oonly one OpenSource class-library: GNU Classpath.
Also important is, that it was created, because there existing before no OpenSource Java library. If there would be existing already an OpenSource Java under the Apache or BSD license, then it would never be started, I think.
2005 Apache started the Harmony project. Still today I can't understand, how so much motivation can be existing, to begin a new OpenSource Java, where already an OpenSource Java exists (GNU Classpath), where it is allowed to link (statical and dynamical) against other files of any other license.
The Apache people have started the Harmony-project, because they are unhappy with the GNU Classpath license. But I think, the GNU Classpath people don't have so much problems with other licenses.
For example the GPL 3 will be allowing generelly to link against other OpenSource files.
And Tom Tromey planned to integrate the Eclipse Compiler for Java (ecj), which is licensed under the Eclipse license (and not any GNU lincense) in the new gcj/gcjx (a frontend for the GCC):
So I think, there existing for GNU Classpath people no fears of contacts with other OpenSource-licenses.
The things, why GNU Classpath don't working together on Apache Harmony is that GNU Classpath
- existing long before Apache Harmony
- is much more advanced
- don't understand (like me), why Apache have started a new project, where alaredy GNU Classpath exists.
But if Sun makes its Java OpenSource, then the code of this Java exists much longer then the GNU Classpath code. And the code is much more advanced and stable then the GNU Classpath code.
I think, in this case it would make sense, that GNU Classpath developer change from its Java implementation to Suns implementation.
The only problem which then exists, to show the developers a new way. The wind have changed. It is no longer necessary to rewrite the JDK. The new activity is to help improving Suns Java. And accept, that possible no of the GNU Classpath code (and so of your six years old work) would be integrated in Suns JDK.
And now a question to GNU Classpath people (ans especialy to the leader ark Wielaard:
The qoal is to bring Apache Harmony, GNU Classpath and Suns Java together.
What must be happen to leave GNU Classpath and working instead of that on Suns Java. Improving it and fixing bugs on it? (more then one answer is allowed)
a) "Nothing. I am only familiar with GNU Classpath. It needs to much time, to undertand other code"
b) "It must be a GNU project. Sun must sign a Copyright-Assignment, to give the copyright to the FSF, only then I would work on the code"
c) "under the GPL + linking exception (like the GNU Classpath license)"
d) "under a GPL license"
e) "under a LGPL license"
f) "the BSD license is ok. If ift oukld be BSD, I would also change to Suns Java"
g) "the Apache license is ok ..."
h) "the CDDL license is ok ..."