Hi, You have to define the maven repo (and being able to access to the repo) in etc/org.ops4j.pax.url.mvn.cfg. More over, the user launching karaf has to have the write permission.
Is it the case ? Regards JB -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://wwx.talend.com ----- Reply message ----- From: "DERIES Sebastien" <[email protected]> To: "[email protected]" <[email protected]> Subject: karaf feature absolute path problem Date: Mon, May 26, 2014 1:53 pm Hi all, I’m using apache-karaf-3.0.0.RC1, with Java 8u20 on Linux Red hat 6.2. We use karaf features to install our bundles and configuration files into KARAF. Example:<feature name="language"> <configfile finalname="/etc/package.lang.cfg">mvn: package.lang/language/0.0.1-SNAPSHOT/cfg</configfile> <bundle start-level="70">mvn:package.lang/language/0.0.1-SNAPSHOT</bundle></feature> Everything works perfectly fine when we install and run our application on our development machine. However when we run a copied version of karaf on our integration platform, KARAF cannot find the configuration file. We got a File not found exception saying that karaf wants a file on the KARAF_HOME/etc development machine instead of getting the configuration file from the integration platform KARAF_HOME/etc. example: /useraccounts/myuser/KARAF/ apache-karaf-3.0.0.RC1/etc/package.lang.cfg instead of ./etc/package.lang.cfg It seems that feature installation uses absolute path for configuration files instead of a relative path. Is there a way to configure features to use relative path? Or to set the a feature home directory? Thanks a lot. Sébastien Deries Tel. : + 33 (0)4 92 96 31 52 [email protected] [@@ THALES GROUP INTERNAL @@]
