We are using Karaf 3.0.1 on a system which doesn't have an internet connection. For installation of additional feature (ActiveMQ, Camel), we created a local maven repository. Our application bundles were initially installed via file:/// (when we still used Karaf 2.3.3), with 3.0.1 we now also use a maven repository due to the still unsolved 30-seconds-timeout problem with file:///.
Recently we faced a problem of bundles not being updated and found out that in Karaf 3.0.1, all additional feature bundles are installed in .m2 in the user's home directory, and they seem to only be updated if bundles there have a time stamp older than 24 hours. Question 1: Is is possible to configure Karaf 3.0.1 to not create and use a .m2 repository in the installing user's home dir? I have searched the options in org.ops4j.pax.url.mvn.cfg but it wasn't obvious to me how to achieve this. I'd like to avoid side-effects introduced by .m2 usage, and since bundles are anyways not fetched from remote, I don't see an advantage. (Using org.ops4j.pax.url.mvn.globalUpdatePolicy=always might solve the update problem as a workaround - but doesn't look like a clean solution to me.) Question 2 (rather generic, I know): Is there some best practice how to install an application in Karaf in a production environment? Thanks, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-3-0-1-how-to-avoid-usage-of-m2-repository-tp4033016.html Sent from the Karaf - User mailing list archive at Nabble.com.
