Linked by Thom Holwerda on Wed 9th May 2007 10:08 UTC, submitted by Ford Prefect
Java Sun Microsystems has announced the release of an open-source version of its Java Development Kit for Java Platform Standard Edition. Sun has contributed the software to the OpenJDK Community as free software under the GNU GPLv2. Sun also announced that OpenJDK-based implementations can use the JCK (Java SE 6 Technical Compatibility Kit) to establish compatibility with the Java SE 6 specification. OpenBSD has already started importing the release.
Thread beginning with comment 238902
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Ah well
by smitty on Wed 9th May 2007 19:53 UTC in reply to "RE[5]: Ah well"
smitty
Member since:
2005-10-13

Exactly. On a related note, does anyone know what the difference is between the GPL + Classpath exception and the LGPL?

Reply Parent Score: 2

RE[7]: Ah well
by trenchsol on Wed 9th May 2007 20:27 in reply to "RE[6]: Ah well"
trenchsol Member since:
2006-12-07

With entire JDK and class libraries under LGPL someone could release competing and proprietary version of JDK that includes SUN's own code. This way, SUN made sure that all other JDK's that include SUN's code will be under GPL.

SUN is protecting their intelectual property, and in the same time enabling Linux and other vendors to create optimized and integrated binaries under GPL.

.NET integrates with Windows, and now Java integrates with Solaris and Linux.

Reply Parent Score: 4

RE[8]: Ah well
by BluenoseJake on Wed 9th May 2007 23:56 in reply to "RE[7]: Ah well"
BluenoseJake Member since:
2005-08-11

And somebody will also integrate it with Windows. Might not change the balance of power as much as you think

Reply Parent Score: 2

RE[7]: Ah well
by andrewg on Wed 9th May 2007 21:02 in reply to "RE[6]: Ah well"
andrewg Member since:
2005-07-06

Good question. I did a little research. It looks like the Classpath exception is less restrictive than the LGPL.

The LGPL seems to require two additional things:


1. It must be possible to link the program to a new / modified version of the LGPL module being used. So if you statically link the LGPL module you would have to provide your object or source code to the customer.

2. The software linking to the LGPL module can be licensed under any terms BUT the terms must allow for modification but the customer and reverse engineering for debugging the modification.

See http://en.wikipedia.org/wiki/GPL_linking_exception for details.

Edited 2007-05-09 21:18

Reply Parent Score: 4