|
From: <php...@li...> - 2009-07-08 18:57:53
|
> 2.0 and a few php license files. Declares itself at . > spec and changelog as lgpl 2.0 The lgpl applies to the java.c and the JavaBridge.inc source files. But since these files are not used anymore, it really doesn't matter. Regards, Jost Boekemeier 8. Jul 2009 5:38 nachm. schrieb am < php...@li...>: Hello, I found the following guides about licenses incompatibilities: http://www.gnu.org/philosophy/license-list.html http://www.apache.org/licenses/GPL-compatibility.html and the list http://www.opensource.org/licenses about OSI approved ones. I found that bridge original code has, at least, "in-line-text-own-license", gpl 2.0 and a few php license files. Declares itself at .spec and changelog as lgpl 2.0. It seems inconsistent, IFAIK. LGPL 3.x seems to be a good alternative, with compatibility with Apache 2.x license and good protection for the project. It seems, at the first review, that other licenses are at the /unsupported directory. Regards. Andre Felipe Machado http://www.techforce.com.br ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ php-java-bridge-users mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users |