Hi, We just rewrite the package name of ConcurrentLinkedHashMap to avoid the version conflict, as ConcurrentLinkedHashMap could be use in the container where the camel is deployed into.
I just updated the version to 1.4.2 in the camel master branch. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 29, 2015 at 2:14:05 AM, ndjensen (ndjen...@gmail.com) wrote: > Camel ticket 4345 added ConcurrentLinkedHashMap. > https://issues.apache.org/jira/browse/CAMEL-4345 > > It seems that ConcurrentLinkedHashMap is included in the camel-core jar but > with a different package name of > org.apache.camel.com.googlecode.concurrentlinkedhashmap. What is the reason > that ConcurrentLinkedHashMap is not a normal dependency and is instead > repackaged and included inside camel-core? Are there any plans to shift it > to be included like other dependencies? > > Besides the dependency oddity, are there plans to keep camel's copy of > ConcurrentLinkedHashMap up to date? Currently the pom files in camel > indicate it's using ConcurrentLinkedHashMap version 1.4 but version 1.4.2 is > available. https://code.google.com/p/concurrentlinkedhashmap/wiki/Changelog > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-s-plans-for-ConcurrentLinkedHashMap-tp5762189.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
