Hi, CamelBlueprintHelper just creates one test bundle and it will look up the bundles in the class path to install them. I suggest you to massage your class path to exclude the test classes bundle or you just put the test into your test classes bundle.
-- 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/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tuesday, October 8, 2013 at 8:43 AM, Andre Piwoni wrote: > Within a maven project that creates bundle I have a test class that extends > CamelBlueprintTestSupport with blueprint descriptor under OSGI-INF/blueprint > directory. > It seems that CamelBlueprintHelper creates two bundles that point to the > same Blueprint XML. > > One bundle is created for Bundle-SymbolicName=testClassName using blueprint > under OSGI-INF/blueprint directory and another is created by scanning for > bundles in all META-INF/MANIFEST.MF resources, one of these bundles happens > to be a bundle for project containing test class and pointing to the same > Blueprint XML. > > This seems to be causing all sorts of issues and I was wondering how to > handle this problem. > > Thanks, > Andre > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-Issues-tp5741066.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
