Just for completeness: In the meantime, I'm using Karaf 3.0.2. I now have the repository for my own bundles in an extra folder under the Karaf home directory, and have added this folder to the org.ops4j.pax.url.mvn.defaultRepositories.
All entries in org.ops4j.pax.url.mvn.repositories have been removed, since there should be no extra things installable in the production environment. All the features I need are included in a custom distribution which I have built - works great. When I need an update for my own bundles, I just copy them into my special folder (overwriting what is already there), including an updated feature xml file if needed (additional / removed bundles). Then I remove the feature, update the repo, and re-install the feature. Rather rough way, but it works for all cases. I'm thinking of some improvement (ACE etc.), but that might be another thread. No more extra mvn dirs are created, so that problem is solved. Thanks again for the help! Best Regards, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-3-0-1-how-to-avoid-usage-of-m2-repository-tp4033016p4036357.html Sent from the Karaf - User mailing list archive at Nabble.com.
