On 24 Jul 2014 23:06, "thully" <[email protected]> wrote: > > I just noticed that after I replied. In any case, the main problem with what > you've suggested is that it removes .m2 entirely. What I want is to keep .m2 > as an available repository, but *not* to copy the entire system repository > there. That seemed to be how it worked in Karaf 2.2.11 - is there a way to > get this behavior on 3.0.1? (using 3.0.2 isn't an option until it is > released...) >
You could try just adding your .m2 repository to org.ops4j.pax.url.mvn.repositories (ie lock things down as per those instructions, but then explicitly add .m2 back as a snapshots+releases repository). That should let Pax-URL use it as a source of bundles, but not cache extra content there. > -- > View this message in context: http://karaf.922171.n3.nabble.com/Disabling-local-repository-creation-on-Karaf-3-tp4034426p4034434.html > Sent from the Karaf - User mailing list archive at Nabble.com.
