If an Apache module *requires* a non-ASL-friendly library in order to
be used, then I think that's the sticking point.  Although, I don't
know how far we take that.  All of our Java modules require a JVM,
which isn't compatible either.

On Tue, Sep 25, 2012 at 10:38 AM, Sam (Stephen Samuel)
<samspad...@gmail.com> wrote:
> That's a fair point about them trying to circumvent the original intent of
> the zeromq authors for an LGPL product. I agree with you now you have
> pointed that out.
>
> There is a special exception on the LGPL license for the Java driver which
> I think covers this kind of case:
> https://github.com/zeromq/jzmq/blob/master/COPYING.LESSER (final paragraph).
>
> But the Java driver is a pain as you have to compile it yourself (there is
> no binary for it).
>
> Akka is on maven central.
> http://search.maven.org/#browse%7C1007422773
>
> Also you don't need Scala on your classpath to compile the camel zeromq
> component. You will if you wanted to compile Akka of course.
>
> Shall we put this in camel extra's and be done ?
> If so, is that just a normal patch submitted to camel jira as per normal ?
>
>
>
>
> On 25 September 2012 15:27, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
>> On Tue, Sep 25, 2012 at 4:13 PM, Sam (Stephen Samuel)
>> <samspad...@gmail.com> wrote:
>> > I don't think the word "hack" is quite right. The Akka Zeromq driver is
>> > totally legit. I imagine they wrote it for the same reason - they wanted
>> to
>> > keep Akka APL instead of GPL.
>> >
>>
>> Its a hack in the sense that Akka went around the intent from ZeroMQ
>> which is that their product is LGPL licensed.
>> If they wanted people to integrate with ZeroMQ using other licenses
>> then IMHO it would be better if ZeroMQ had dual licenses for its
>> drivers.
>>
>> Since we cannot use a driver from the "source" eg ZeroMQ project, and
>> have to defer to Akka project which is also Scala based (requiring
>> Scala on the JVM) is imho going a bit far, and in the area of being a
>> "hack".
>>
>> The other Camel components do not do this. So its a bit controversial
>> if the ASF community of Camel is interested going down this road.
>>
>> And also the Akka releases is not published to maven central. Its not
>> a blocker though. But software released to maven central is preferred.
>> Its a bit of pain to have to rely on to many 3rd party maven repos.
>>
>> > On 25 September 2012 15:08, Claus Ibsen <claus.ib...@gmail.com> wrote:
>> >
>> >> Hi
>> >>
>> >> See ticket
>> >> https://issues.apache.org/jira/browse/CAMEL-5557
>> >>
>> >> As this component uses a bit of a "hack" to avoid using LGPL I would
>> >> like fellow riders thoughts on this contribution?
>> >>
>> >> There is a number of comments on this ticket, I suggest to read to get
>> >> up to speed.
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> Red Hat, Inc.
>> >> FuseSource is now part of Red Hat
>> >> Email: cib...@redhat.com
>> >> Web: http://fusesource.com
>> >> Twitter: davsclaus
>> >> Blog: http://davsclaus.com
>> >> Author of Camel in Action: http://www.manning.com/ibsen
>> >>
>> >
>> >
>> >
>> > --
>> > -Sam
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cib...@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
>
> --
> -Sam

Reply via email to