Linked by Thom Holwerda on Sun 2nd Apr 2006 18:31 UTC
Permalink for comment 110573
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
More News »
Sponsored Links



Member since:
2005-08-20
PS- Would there technically be any problem with an Apache JVM using GPL ClassPath .class-es? After all, they aren't linking to them, merely reading them, and in the case of JIT, compiling them but not distributing them. I really don't see the problem, but IANAL.
There would be no legal trouble with distributing classpath and harmony together. I'm about a month and a half behind on the dev mailing list reading, but to the best of my knowledge the classlib/vm interface used will be classpath compatible so it should be possible.
However, classpath will not be distributed as part of the project and so the combination will probably never be certifiable Java. They tried hard to come up with a way for Apache to distribute gpl'ed code, but the process was completely stalled when IBM and Intel came along and donated so much code and that was basically the end of it.