Hi, I fully agree John here. The feature descriptor just points to maven coordinates. Therefore I think we are license safe.
Regards, achim sent from mobile device Am 10.01.2014 01:30 schrieb "John D. Ament" <john.d.am...@gmail.com>: > Right, but is there an actual dependency on something LGPL/GPL here? > The file in question is an instruction to a karaf instance on how to > install something (e.g. hibernate). Hibernate isn't actually > distributed, simply commands that tell the instance where to get > hibernate. > > On Thu, Jan 9, 2014 at 6:41 PM, Johan Edstrom <seij...@gmail.com> wrote: > > It applies to anything licensed under ASF Licenses. > > Hibernate is probably a good example, the Apache Camel Hibernate > components > > are housed outside ASF, in a 3rd party repo. > > Since that component is compiled against GPL code it isn't ASF compatible > > anymore. > > > > > > On Jan 9, 2014, at 4:14 PM, John D. Ament <john.d.am...@gmail.com> > wrote: > > > >> Well, since there is no compile time dependency on hibernate, is there > >> actually a licensing issue? > >> The binary is referenced, but not compiled against in Apache code. > >> > >> On Thu, Jan 9, 2014 at 5:35 PM, Krzysztof Sobkowiak > >> <krzys.sobkow...@gmail.com> wrote: > >>> Hi > >>> > >>> I have some licensing questions. > >>> > >>> I have found following page http://www.apache.org/legal/3party.htmlwhich > >>> defines 3 categories of third party licenses. According to this page > LGPL > >>> v2.1 is category X, but further remark says, the LGPL-v2.1-licensed > work can > >>> be listed as system requirements but can not be included by Apache > >>> products. I'm not good in licensing but I try to understand it. Is the > >>> category of LGPL really B (and the page should be corrected) or is > the LGP > >>> category X. In the second case, can we still list Hibernate in Karaf > >>> features (e.g. using the remark about listing of system requirements)? > >>> > >>> Assume following use cases of third-party work usage: > >>> 1. reference 3rd-party library as (maven) dependency and use the > classes in > >>> ASF code > >>> 2. reference 3rd-party library as (maven) dependency and use the > classes > >>> only in ASF configuration files (e.g. blueprint.xml) > >>> 3. include/copy some unmodified 3rd-party code (e.g. some classes) in > ASF > >>> project > >>> 4. include/copy some 3rd-party code (e.g. some classes) in ASF project > and > >>> modify it > >>> 5. list some 3rd-party libraries in Karaf features, but not include > them as > >>> binaries in one of the Karaf distributions > >>> 6. list some 3rd-party libraries in Karaf features, and include them > as > >>> binaries in one of the Karaf distributions in system repository > >>> > >>> Could anybody please answer which of above points are allowed for > following > >>> 3rd-party works > >>> a. category A as the whole category - I assume, all above use cases are > >>> allowed in this category, is it ok? > >>> b. category B as the whole category > >>> c. category X as the whole category > >>> d. LGPL > >>> e. GPL > >>> f. EPL > >>> > >>> I have chosen Karaf as sample ASF project, but it could be any other > ASF > >>> project, e.g. ServiceMix or Aries > >>> > >>> Do the rules from the page mentioned above apply only for ASF projects > or > >>> for any project licensed under Apache License? > >>> > >>> Best regards > >>> Krzysztof > >>> > >>> > >>> > >>> On 03.01.2014 11:51, Jean-Baptiste Onofré wrote: > >>> > >>> LGPL is category B (not X), so we can reference it but not "include" > it: > >>> it's what we do. > >>> > >>> FYI, in Karaf 3.0.0, I've already added a hibernate feature. > >>> > >>> Regards > >>> JB > >>> > >>> On 01/03/2014 11:46 AM, Freeman Fang wrote: > >>> > >>> Though it's a very useful feature, I'm not sure if we can add it in > >>> Karaf, as Hibernate is under LGPL license, can we? > >>> －－－－－－－－－－－－－ > >>> Freeman(Yue) Fang > >>> > >>> Red Hat, Inc. > >>> FuseSource is now part of Red Hat > >>> > >>> > >>> -- > >>> Krzysztof Sobkowiak > >>> > >>> JEE & OSS Architect | Technical Architect @ Capgemini > >>> Capgemini | Software Solutions Center | Wroclaw > >>> e-mail: krzys.sobkow...@gmail.com | Twitter: @KSobkowiak > > >
