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 238847
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Ah well
by fretinator on Wed 9th May 2007 16:57 UTC in reply to "RE[2]: Ah well"
fretinator
Member since:
2005-07-06

Using a compiler to compile your code IS NOT a derivative work. Even linking in GPL libraries (thus the LGPL) is not a derivative work. So these arguments are specious. You can create GPL works with C#, and you will be able to create closed-source products with java. You just cannot create a closed-source _VERSION_ of java (as the previous poster mentioned). The good news, is since C# is an open standard (ISO), you can produce an open-source version of the C# language, and thus we have Mono. Nevertheless, you can most certainly create a closed-source Mono project if you want, but obviously most would use C# to create closed-source projects.

As an example of an excellent open-source C# application, you just have to look at SharpDevelop. It is an excellent GPL C# application.

Reply Parent Score: 5

RE[4]: Ah well
by Alex Forster on Wed 9th May 2007 18:15 in reply to "RE[3]: Ah well"
Alex Forster Member since:
2005-08-12

(genuine question..)

But, if the Java standard classes are GPL'd, and my Java application uses these standard classes, doesn't my application have to be GPL'd?

Reply Parent Score: 2

RE[5]: Ah well
by fretinator on Wed 9th May 2007 18:26 in reply to "RE[4]: Ah well"
fretinator Member since:
2005-07-06

But, if the Java standard classes are GPL'd, and my Java application uses these standard classes, doesn't my application have to be GPL'd?


No linking to a library and extending a library are two different things. I think this is the reason for the LGPL. You can link to a library in a closed-source app. I assume this will also be true for using Java standard classes in your application.

Reply Parent Score: 4

RE[5]: Ah well
by andrewg on Wed 9th May 2007 18:33 in reply to "RE[4]: Ah well"
andrewg Member since:
2005-07-06

No because the license is GPL with the Classpath exception except for the Hotspot VM which is licensed under GPL only though.

The Classpath exception is:

The Classpath exception was developed by the Free Software Foundation's GNU/Classpath Project (see http://www.gnu.org/software/classpath/license.html). It allows you to link an application available under any license to a library that is part of software licensed under GPL v2, without that application being subject to the GPL's requirement to be itself offered to the public under the GPL.

Source: http://www.sun.com/software/opensource/java/faq.jsp.

Reply Parent Score: 5