The main driver for this license change is the clause 6 in the
LGPLThe issue here is that it requires proprietary applications, using LGPL libraries, to provide a way to debug them or reverse-engineer them for debugging purposes.
That is not always business-friendly, as it creates concerns about the security and safety of proprietary code, that may be considered trade secrets by their owners.
This clause is considered "viral" for Java and many businesses are starting to either avoid LGPLed libraries, or to watch them with active suspicion.
I'd rather have you make your own opinion, here is a list of articles that may give you a good starting point:
http://article.gmane.org/gmane.comp.jakarta.poi.devel/5900http://www.fsf.org/licensing/licenses/lgpl-java.html/view?searchterm=lgplhttp://slashdot.org/developers/03/07/17/2257224.shtmlYou can also google on the topic.
We found that the Apache License v2.0 does not have this "viral" constraint, while still permitting free use and redistribution for any purpose.
The
Apache license FAQ has clear and understandable explanations about what can and cannot be done with it.
We hope this helps,
The JPPF Team
