I'm using Karaf 2.1.2. I just discovered that when I run Karaf as a service (using the wrapper), bundles specified with the "mvn:" protocol will not be resolved unless they exist in the system folder under the Karaf installation.
This is not necessarily a problem for me. In production all my bundles will be packaged in the system folder and I do not want Karaf to look elsewhere. I've actually wanted to prevent Karaf from looking anywhere in the local system folder since I want to be very sure what bundles are used in production. In my development environment it is very convenient to resolve bundles directly in my local maven repository without having to copy them to the system folder in the Karaf installation. Since I normally run Karaf from the command line during development this works well since in that case Karaf does resolve "mvn:" bundles in my local maven repository. Is this as designed? What can I rely on? Ideally I would like to turn on / turn off the ability to search outside the system folder for bundles - regardless if I'm running Karaf from the command line or as a service. /Bengt
