You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2012/06/14 15:25:42 UTC
[jira] [Resolved] (CAMEL-5342) Shaded concurrentlinkedhashmap-lru
conflicts with existing jar
[ https://issues.apache.org/jira/browse/CAMEL-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5342.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
2.9.3
Updated the shade plugin configure for it.
> Shaded concurrentlinkedhashmap-lru conflicts with existing jar
> --------------------------------------------------------------
>
> Key: CAMEL-5342
> URL: https://issues.apache.org/jira/browse/CAMEL-5342
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.2
> Reporter: Mikhail Moussikhine
> Assignee: Willem Jiang
> Fix For: 2.9.3, 2.10.0
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira