camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Manes (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5342) Shaded concurrentlinkedhashmap-lru conflicts with existing jar
Date Fri, 08 Jun 2012 04:59:22 GMT


Ben Manes commented on CAMEL-5342:

CLHM v1.3 includes an OSGi manifest, if that helps.
> Shaded concurrentlinkedhashmap-lru conflicts with existing jar
> --------------------------------------------------------------
>                 Key: CAMEL-5342
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.2
>            Reporter: Mikhail Moussikhine
>            Assignee: Willem Jiang
> Package com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru is included/shaded
inside the camel-core jar.
> It is not very nice if concurrentlinkedhashmap-lru.jar is already on the path. It is
a deal breaker, if their versions are different. For example cassandra-1.1.1 requires ConcurrentLinkedHashMap$Builder.maximumWeightedCapacity(),
which is missing from the version included in camel.
> It would be nice if concurrentlinkedhashmap-lru was included as a normal dependency.
Comment in the pom.xml says "Shade the googlecode stuff for OSGi". Well, if that is strictly
required, maybe it could be better included in camel-core-osgi package.
> In any case, if it must be shaded at all, it would be safer to use relocation property
of the maven-shade-plugin. In this case, camel could stay with the version it wants, without
conflicting with explicit dependencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message