Navigation

RSS 2.0 New Entries Syndication Feed Atom 0.3 New Entries Syndication Feed

Show blog menu v

 

General

Use it

Documentation

Support

Sibling projects

RIFE powered

Valid XHTML 1.0 Transitional

Valid CSS!

Blogs : Archives

< Groovy release fixes all show-stopper bugs   RIFE 1.0 released >
LGPL for Java, but with Apache's blessing

RIFE has been licensed under LGPL for quite a while because I want to have the developer protections that it offers (ie. changes have to be released as open source under the same license). Sadly, there has been much controversy about LGPL's usefulness in Java projects. There also seems to be a consensus that LGPL projects will never be used in commercial products due to the doubt and uncertainty that surrounds it. Finally, Apache seems the have major problems with LGPL and takes a long time to make up their mind about it.

So I'm considering relicensing RIFE under another license which offers the same kind of developer protection but is not shunned for commercial usage. The candidates seem to be CPL, MPL or CDDL. The first one has Apache's blessing and the last two will soon be accepted for binary inclusion in Apache projects. I quite like the sound of CDDL, but there seems to be a lot of FUD around it. The connection with Sun doesn't seem to be liked by many, but it seems like the merely tried to improve MPL.

What are your thoughts about CDDL, is it a good choice for an open-source Java web application framework or should I look for something else? Are other licenses with the same developer protection worth considering?

posted by Geert Bevin in RIFE on Aug 25, 2005 10:51 PM : 4 comments [permalink]
 

Comments

Re: LGPL for Java, but with Apache's blessing
No specific comments about the license choices you've listed - but I'd try delaying a decision until the Apache and FSF legal teams have ironed out their stance to the Harmony project licensing.

These discussions span the ASL2, GPL, GPL+Exception and I believe the LGPL has also been mentioned.
Re: LGPL for Java, but with Apache's blessing
Well, haven't they at least made part of their mind up?

http://mail-archives.apache.org/.../%3c96D75844-B15A-45E3-BF8D-5CF4517A09E2@apache.org%3e

-Anders
Re: LGPL for Java, but with Apache's blessing
The biggest drawback to the CDDL is that it is not currently compatable with the GPL: therefore, code released under the GPL cannot link to code released under the CDDL. I expect that the differences will be reduced in the next version of the GPL such that the MPL/SPL/CDDL and others along that line will be compatable, but 1) I could be wrong, and 2) even if that comes to pass, it doesn't help right now.

Until the next versions of the GPL and LGPL become available, my library is dual-licensed under the LGPL and the CDDL.

Re: LGPL for Java, but with Apache's blessing
Thanks for the comment David, I think I will dual license under CDDL and LGPL too. It seems like that all situations are covered and as a developer you're still protected.

Add a new comment

Comments on this blog entry have been closed.

< Groovy release fixes all show-stopper bugs   RIFE 1.0 released >
 
 
 
Google
rifers.org web