Added Jira ticket: https://issues.apache.org/jira/browse/KARAF-4707 <https://issues.apache.org/jira/browse/KARAF-4707>
Thanks, Alex soto > On Sep 11, 2016, at 1:23 AM, Jean-Baptiste Onofré <[email protected]> wrote: > > Good idea. > > Can you create a Jira about that ? > > Thanks, > Regards > JB > > On 09/10/2016 08:43 PM, Oliver Lietz wrote: >> On Friday 09 September 2016 15:04:16 Alex Soto wrote: >>> Thank you! This worked now: >>> >>> <feature name="pax-url-handler"> >>> >>> <bundle>mvn:org.ops4j.base/ops4j-base-util-property/1.5.0</bundle> >>> <bundle>mvn:org.ops4j.base/ops4j-base-lang/1.5.0</bundle> >>> >>> <bundle>mvn:org.ops4j.pax.swissbox/pax-swissbox-property/1.8.2</bundle> >>> <bundle>mvn:org.ops4j.pax.url/pax-url-commons/2.4.7</bundle> >>> <bundle>mvn:org.ops4j.pax.url/pax-url-classpath/2.4.7</bundle> </feature> >>> >>> <feature name=‘my-feature' version='${project.version}'> >>> >>> <feature prerequisite="true">pax-url-handler</feature> >>> >>> <configfile finalname="${karaf.etc}/my.config.cfg"> >>> classpath:my.config.cfg >>> </configfile> >>> >>> >>> So the config file is now correctly read from the class path. I think it >>> can be argued that deploying config files from the class path is the most >>> common scenario, so it may be useful to have the classpath URL handler >>> already preloaded as part of standard Karaf, otherwise the ability to >>> deploy from a resource becomes very obscure. Even more obscure, given that >>> there are not examples on how to do this. >> >> At least having a feature in Karaf for pax-url-classpath (like we have for >> wrap) would be nice. >> >> Regards, >> O. >> >>> Thanks and best regards, >>> Alex soto >> [...] >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
