Hi, As camel can be deployed into lots container and it can run as stand alone server, so we cannot change the dependency as you want. With help of the dependency exclusion, you can resolve the issue in your pom.
-- 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 March 13, 2014 at 2:38:38 AM, Knut-Håvard Aksnes ([email protected]) wrote: > I am using camel-restlet (2.12.3) in a war project and just discovered that > the dependencies doesn't look good. There are at least two problems. > > 1) With a webapp we need to add a dependency to org.restlet.ext.spring as > documented in camel-restlet. The problem being that the documentation > specifies the group id of org.restlet.jee which depends on > org.restlet.jee:org.restlet which is not the same as > org.restlet.jse:org.restlet which is a dependency for camel-restlet > > 2) According to the restlet documentation org.restlet.jee is the correct > edition to use for war's so an exclusion of org.restlet.jse:org.restlet > should be put on camel-restlet + an extra dependency to > org.restlet.jee:org.restlet > > 3) There are still mess in the spring dependencies: org.restlet.ext.spring > depend on spring-asm which has been merged into spring-core in recent spring > versions so a dependency exlusion is needed for > org.springframework:spring-asm. In addition > org.springframework:spring-expression should most likely be pinned to a > version compatible with the one used for the camel build (3.2.5.RELEASE) > > I am still not sure if this will work as I don't in any way consider myself > an expert on restlets and haven't had time to test this at all yet.Maybe all > of this can be wrapped as a separate camel component (Or just a maven bom) > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Dependency-mess-with-camel-restlet-tp5748721.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
