www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: transitive 3rd party dependencies
Date Sun, 29 Jun 2014 11:36:16 GMT
Hi Kevan!

If you build camel-infinispan by your own, Maven will download the required
dependencies (also the prohibited dependencies) and it will work.

If you run camel-infinispan without the prohibited dependencies in your
classpath, you will end up with ClassNotFound exceptions. In general, our
users use some Maven plugins to collect all required dependencies (if they
do it not by hand) and put they together in a WAR/ZIP/... file.
If a user has problems to collect the required dependencies, we point him
to our pom.xml file and the Maven dependency plugin. We do not provide
additional instructions (as we release 170+ components with each release
which have totally different dependencies).

We are planning to build a new 2.13.x release next week. In this release,
we fixed this issue by using a newer version of jboss-marshalling which is
now ASL 2.0 [1].




Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member


On Thu, Jun 26, 2014 at 10:43 PM, Kevan Miller <kevan.miller@gmail.com>

> On Thu, Jun 26, 2014 at 1:03 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>> One of our artifacts (camel-infinispan) has a dependency
>> to infinispan-core (ASL 2.0) which has a dependency to jboss-marshalling
>> (GNU LGPL). This means:
>> - If you build the Camel release, it will download the prohibited jar via
>> the Maven dependency resolution (is this a "deliberate action"?).
> Maybe I should have called it an "informed action". I would not call this
> an informed action. However, the fact that maven downloads the jar is not a
> problem.
> - You can compile the camel-infinispan component without the need of the
>> prohibited jar.
>> - You cannot execute the camel-infinispan junit tests without the
>> prohibited jar.
>> - You cannot use the camel-infinispan component without the prohibited
>> jar.
> OK. So, this is true, even if I build camel-infinispan myself? Do you
> provide instructions to your users on how they can get camel-infinispan
> working? If so, what are they?
>> I looking for clarification whether this is an issue or not and, if it's
>> an issue, what the appropriate action the Camel PMC should do.

View raw message