Thread: [Php-java-bridge-users] found multiple licenses in the code base and docs

Hello,
I was trying to clean more warnings at Debian packaging and found multiple
licenses in the code base and documentation.
Actually, some non-standard OSI classified ones.
There are files licensed under "in-line-license-text" written at them. Mostly by
Jost.
And maybe, some may be potentially conflicting.
Do we have some license expert at the list?
Please, read the list of licenses I found at the CVS head /debian/copyright file.
You can search text for the names of the licenses at the source.
Many of the licenses are under the "unsupported" directory, and included at
borrowed code.
But some of inconsistencies are at bridge original code.
I guess these bridge original code should be under the same license. And a
careful evaluation of the borrowed code from other projects should be done.
What is the best route?
Regards.
Andre Felipe Machado
http://www.techforce.com.br

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

> 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

Hi Andre,

isn't it possible to exclude the examples libs from the distribution?

The only files necessary are the libraries:

JavaBridge.jar (MIT + PHP + Apache 2 License)
php-servlet.jar (MIT)
php-script.jar (MIT)

and the PHP files:

Java.inc (MIT)
JavaProxy.inc (MIT)

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

Correction:

The only files necessary are the libraries

JavaBridge.jar (MIT + PHP + Apache2)
php-servlet.jar (MIT)
php-script.jar (MIT)

and the PHP files

Java.inc (MIT)
JavaProxy.php (MIT)

Regards,
Jost Boekemeier

8. Jul 2009 8:44 nachm. schrieb am "Jost Bekemeier" <
jos...@go...>:

Hi Andre,

isn't it possible to exclude the examples libs from the distribution?

The only files necessary are the libraries:

JavaBridge.jar (MIT + PHP + Apache 2 License)
php-servlet.jar (MIT)
php-script.jar (MIT)

and the PHP files:

Java.inc (MIT)
JavaProxy.inc (MIT)

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/ph...
------------------------------------------------------------------------------
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

Hello,
By reading the Gpl faq, I discovered that it is possible to distribute
"aggregated" sw with gpl, given that obeying its respective license
terms.
Aggregate is explained as something at the same media, but not linked
nor modified nor included at other code.
So, if the multiple licenses listed at the /debian/copyright at CVS head
allow this "aggregation" of unmodified code, it may be ok for
the /unsupported directory, for example.
But careful analysis with linked sw among them.
The PHP license is listed as incompatible with gpl.
Could such code portion at JavaBridge.jar be relicensed as gpl? Are all
their code authors reading this list?
MIT and Apache License 2.0 are listed as compatible with gpl.
Regards.
Andre Felipe



Em Qua, 2009-07-08 às 21:06 +0200,
php...@li... escreveu:
> Correction:
> 
> The only files necessary are the libraries
> 
> JavaBridge.jar (MIT + PHP + Apache2)
> php-servlet.jar (MIT)
> php-script.jar (MIT)
> 
> and the PHP files
> 
> Java.inc (MIT)
> JavaProxy.php (MIT)
> 
> Regards,
> Jost Boekemeier