As we are don’t suppose to change the third part dependencies unless there is a security issue. You have to do the excludes setting yourself.
But I think we can update the servlet API dependency to 3.1[1] in the camel master branch. [1]https://issues.apache.org/jira/browse/CAMEL-9513 -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 14, 2016 at 12:09:28 AM, nascha (nadia.schach...@avature.net) wrote: > This is very similar to issue CAMEL-8803 > which was about > camel-jetty9: "two conflicting and different versions of several classes > [are included]. Both the Servlet API 3.0 version and Servlet API 3.1 version > are included as (transitive) dependencies." > > This same issue is caused in 2.16.1 by camel-http-common which depends on > geronimo-servlet_3.0_spec > So a project with both camel-jetty (now using 3.1) and camel-http4 (which > includes camel-http-common, now using 3.1) will have the two conflicting > specs. > > Could this be changed? > Thanks. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-http-common-2-16-1-includes-Servlet-API-3-0-tp5776203.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
