Hi Yeah sounds strange as they are both from the very same jar - camel-core.
btw you do not need to type cast you can use the api on camel context. which we may consider removing the @deprecation as its more annoying than good. And instead of type cast we should add an adapt(T) method for ppl to use if they really wanna work wit the model camel context On Thu, Jan 22, 2015 at 12:46 PM, geppo <geppore...@gmail.com> wrote: > Hi, I've written a JUnit test in Eclipse for a Camel route. > It has been working fine for days, but now it doesn't startup failing in the > CamelTestSupport.setUp method: > > > > I've tried to cleanup the Maven repository especially the camel-core, > camel-test and junit repositories. > When I right-click on the CamelTestSupport class in Eclipse it says it comes > from the camel-test jar version 2.9.3 (which should match the camel-core) > although I found in the past that Eclipse often lies on which version is > actually using (if you have multiple ones in your Maven repository). > Junit version used should be 4.8.1 (again that's what Eclipse says at > least...). > I suspect it's a problem with libraries versions. > > Any idea? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Cannot-cast-DefaultCamelContext-to-ModelCamelContext-tp5762011.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
