Thanks, Achim! Yes, placing the additional repos in the defaultRepositories would make the resolver to look there even before it checks the local repo. This would solve my problem with newer bundle version, while I assume that the local .m2 repo will still be created.
However, when I place my repos in the defaultRepositories instead of adding them to org.ops4j.pax.url.mvn.repositories, the AetherBasedResolver throws an exception that it cannot find the respective artifacts. It seems that all repos in org.ops4j.pax.url.mvn.defaultRepositories are just neglected. Changing the org.ops4j.pax.url.mvn.disableAether to true or false doesn't make any difference. I'm not sure whether I did something wrong or whether I stumbled over a bug in Karaf 3.0.1. Regards, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-3-0-1-how-to-avoid-usage-of-m2-repository-tp4033016p4033021.html Sent from the Karaf - User mailing list archive at Nabble.com.
