I should make a correction here. I just found out using "target" directory resolves the issues in almost all scenarios (e.g. on our build server and most development machines). But even with this fix, I am able reproduce the issue on some development machines still.
*On those machines, the work-around is to use a shallower directory.* So currently I am using CamelBlueprintTestSupport.setConfigAdminInitialConfiguration() which is part of the recent changes made to this class to resolve the race conditions for ConfigAdmin initialisation that plagued blueprint testing for years. More details here: http://ggrzybek.blogspot.com.au/2015/12/camel-blueprint-test-support.html There is definitely some sort of race condition in that class but it is fairly difficult to track down due to asynchronous nature of OSGi service loading. (useAsynchronousBlueprintStartup() doesn't help.) -- View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-doesn-t-like-6-directories-deep-tp5787192p5787260.html Sent from the Camel - Users mailing list archive at Nabble.com.
