I don't really know. It is not the build itself, but the karaf feature resolver 
the one that pulls the dependency. I've created a brand new build copied from 
jclouds-karaf called `jclouds-karaf-with-azure`, but it presents the same 
Also tried changing the build to not use the local Maven repo, but with no 

Could you try the build locally with all tests, and give a try to the build I 
created in the Jenkins CI too?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Reply via email to