Also, I've noticed that this behavior seems to be new to Karaf 3 - we never had any issues with Karaf 2.2.11 copying system bundles into .m2. Any idea what has changed in Karaf 3 to make this behavior happen, and is there something I can do (changing a setting, or perhaps using a different version of one of Karaf's dependencies) to get the Karaf 2 behavior in Karaf 3? We would just stick with 2.2.x until this is fixed, but at this point we need to support Java 8 ASAP.
If that isn't an option, we could deal with having the local repo as system if it works OK with read-only system repositories. If not, we'll probably put the local repository somewhere else where we can expect write permissions (not .m2, as we don't want to push our artifacts to an existing Maven repository). The extra bundles copies/disk space use is undesirable, though we could put up with it until this gets fixed in Karaf. -- View this message in context: http://karaf.922171.n3.nabble.com/Disabling-local-repository-creation-on-Karaf-3-tp4034426p4034489.html Sent from the Karaf - User mailing list archive at Nabble.com.
