>>>>> Jean-Baptiste Onofré <[email protected]>: > It seems you are chaging the etc/startup.properties.
Slightly. Just adjusting the version of jansi to "debian" (which always point to the current version of a package in the debian repository). I thought I could make the boot scan the debian repository, if it didn't find the bundles in system (ie. first try system and then fall back to the debian repository). > Pax URL is not used here as it's started by the etc/startup.properties (so > startup.properties is read before Pax URL). Ah, ok. So at the time startup.properties is resolved, org.ops4j.pax.url.mvn.cfg with my modification, haven't yet been read? > The Karaf main bootstrap looks into the system folder for the artifact (it's > done in the installAndStartBundles() of Karaf Main). So you have to replace in > the system folder (or use a link here). A symlink would seem like the best idea. It's what I do for the osgi framework and JNA libraries in the lib/boot/ directory. A symlink pointing to the debian version inside the debian repository should do the trick. Does it make sense to keep the modification to org.ops4j.pax.url.mvn.defaultRepositories? Or should I just remove that?
