It turns out that I had an incorrect type of packaging in my pom.xml file.
It should have been packagingbundle/packaging instead of 'jar'. This
enabled the junit to pass.
--
View this message in context:
Thanks for the note, I just update the wiki page of camel blueprint test with
this information.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/)
I've created a custom component (talend) which passes its own junit test.
I've mvn installed it to my local repo.
Now I want to use the component. So I have a separate blueprint project. I
have camel.version set to 2.11.2 and the new component as a dependency in
this project's pom.xml -
As camel-blueprint-test loads the bundle from class path to simulate the OSGi
platform behaviour. If you want to CamelBlueprintTestSupport find your custom
component, you need to add the dependencies of the customer component in your
pom.
--
Willem Jiang
Red Hat, Inc.
Web:
