Re: camel webapp and the licensing stuff

[mickhayes <mi...@gmail.com>]

Hi, 
I looked at this for AMQ 5.4.1.
The ASF Jira bugref. is https://issues.apache.org/jira/browse/AMQ-3491

The offending components LGPL-licensed jaffl and jiffi  have later versions
which are now Apache V2-licensed.
Assuming compatability, *there is no licensing reason to not include a camel
webapp* which includes the Apache V2-licensed versions of jaffl and jiffi.

jaffl 0.5.1 has the LGPLv3 license for the version:
http://mvnrepository.com/artifact/org.jruby.extras/jaffl/0.5.1 

The latest jaffl 0.5.11
http://mvnrepository.com/artifact/org.jruby.extras/jaffl/0.5.11 is Apache v2
licensed, and it has been so since jaffl 0.5.9, see
http://mvnrepository.com/artifact/org.jruby.extras/jaffl 

Jaffl depends on jffi, which WAS LGPL licensed up to 1.0.6 ( 1.0.1 is in AMQ
5.4.1). From 1.0.7 it is Apache V2 licensed:
http://mvnrepository.com/artifact/org.jruby.extras/jffi/1.0.7 

HOWEVER, AMQ-3491 lists another component of concern:
org.jruby.ext.posix:jnr-posix (Copyright Thomas E Enebo), which appears to
be triple-licensed: CPL/GPL/LGPL and depends on multiple other components:
http://mvnrepository.com/artifact/com.github.jnr/jnr-posix/2.0

I haven't had any investigation done on this one.



-----
Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA 

--
View this message in context: http://activemq.2283324.n4.nabble.com/camel-webapp-and-the-licensing-stuff-tp4341201p4387838.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.