Submitted by Shai Almog (not verified) on Sat, 2008-05-24 15:40.
Why not ask?
The source code isn't GPL. Its GPL+CPE which is the classpath exception: In English that means you don't have to publish your own code under the GPL however if you change LWUIT itself you have to publish it under GPL.
Besides that Sun which owns the full copyright of the code is entitled to produce a binary only release with a different license that is often easier for enterprise lawyers to grok. Which is exactly what we do.
So bottom line: use LWUIT freely in any commercial applications! When the source come out you will be able to change it but you will need to publish the LWUIT sources which you changed (not your application!) based on the GPL+CPE license terms.
The GPL+Classpath Exception is a well known license used by the JDK itself and quite a few other projects.
Why not ask?
The source code isn't GPL. Its GPL+CPE which is the classpath exception: In English that means you don't have to publish your own code under the GPL however if you change LWUIT itself you have to publish it under GPL.
Besides that Sun which owns the full copyright of the code is entitled to produce a binary only release with a different license that is often easier for enterprise lawyers to grok. Which is exactly what we do.
So bottom line: use LWUIT freely in any commercial applications! When the source come out you will be able to change it but you will need to publish the LWUIT sources which you changed (not your application!) based on the GPL+CPE license terms.
The GPL+Classpath Exception is a well known license used by the JDK itself and quite a few other projects.