I can confirm it by checking the camel-test-spring-2.11-SNAPSHOT, and I just find a way to fix it. Here is the JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-5915 -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Friday, December 28, 2012 at 7:51 AM, Babak Vahdat wrote: > Hi all > > As I was upgrading an application to the Apache Camel 2.10.3 Release I > realized that there're bunch of class files which are mixed up into the > camel-test-spring-2.10.3.jar JAR @ central: > > http://repo.maven.apache.org/maven2/org/apache/camel/camel-test-spring/2.10 > .3/camel-test-spring-2.10.3.jar > > > Like: > > org.apache.camel.test.AvailablePortFinder > > org.apache.camel.test.junit4.TestSupport > org.apache.camel.test.junit4.CamelTestSupport > Š > Š > > Which all come into this JAR somehow because of this module dependency to > camel-test module etc., but these classes are already there where they > should be: > > http://repo.maven.apache.org/maven2/org/apache/camel/camel-test/2.10.3/came > l-test-2.10.3.jar > > > This seems to be the case by the previous releases as well. I didn't > verify/check any other jars of this release. > > Is this really intentional? > > Babak
