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

You can only create GPL products with Mono (and now, with Java); derivitive works of a GPL program must be released under the same license (that's the entire point of copyleft). Have you read the GPL yet?

Reply Parent Score: -5

RE[3]: Ah well
by computrius on Wed 9th May 2007 16:48 in reply to "RE[2]: Ah well"
computrius Member since:

Derivitive works as in if I create a programming language from the source code of java and call it, say, Lava.. Then I would have to open source THAT.

A program completly unrelated written in the java language is NOT a derivitive work of an open source java.

By your logic anything compiled/written with gcc/g++ c/c++ would have to be open source.

Edited 2007-05-09 16:49

Reply Parent Score: 3

v RE[4]: Ah well
by Almafeta on Wed 9th May 2007 18:48 in reply to "RE[3]: Ah well"
RE[3]: Ah well
by fretinator on Wed 9th May 2007 16:57 in reply to "RE[2]: Ah well"
fretinator Member since:

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:

(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[3]: Ah well
by dylansmrjones on Wed 9th May 2007 18:33 in reply to "RE[2]: Ah well"
dylansmrjones Member since:

Incorrect. You can create proprietary products with mono. It is only the IDE which is GPL.

GCC is GPL'ed too but that doesn't mean applications compiled with GCC becomes GPL. You can create proprietary products using the basic GNU libraries.

You can also create proprietary products with GPL'ed Java. You can claim otherwise as you want to but Sun and FSF have already made clear that it doesn't touch derivative works because of an exception clause (not unlike the way GPL is used for fonts). Heck, you can create proprietary products using GNU Classpath because of that.

Reply Parent Score: 4

RE[3]: Ah well
by trenchsol on Wed 9th May 2007 20:10 in reply to "RE[2]: Ah well"
trenchsol Member since:

Look for 'Classpath exception' on your favourite search engine. It is a clause in JDK license that enables you to mix class libraries that come with JDK with your own proprietary code.

It was the first thing I checked when I heard that J2SE is going to be distributed under GPL.

Reply Parent Score: 3

RE[3]: Ah well
by BluenoseJake on Wed 9th May 2007 23:44 in reply to "RE[2]: Ah well"
BluenoseJake Member since:

Actually, that's false. If you modified the Runtime, then you would have to release the modified runtime as GPL, but anything you write with it is not GPL. Any linking to the runtime is done exactly then, at runtime.

Reply Parent Score: 2