2016-09-10 20:43 GMT+02:00 Oliver Lietz <[email protected]>: > 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. >
Agreed. Maybe raise a JIRA and attach a patch ? > > Regards, > O. > > > Thanks and best regards, > > Alex soto > [...] > > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
