Hi JB, I didn't realize that you could put a jar into the lib directory that way, that's a handy tip to keep in my back pocket. I thought you could only do that with a kar file.
Regards, Ryan On Thu, Dec 5, 2013 at 7:56 AM, Jean-Baptiste Onofré <[email protected]>wrote: > Hi Marco, > > yes, config file can provision any file. NB: careful, Karaf only polls > *.cfg file by default, not *.properties. > > I think that you can use <configfile/> with other resources like /lib or > custom system.extra.package. > > Something like this should do the trick: > > <configfile finalname="/lib/mylib.jar"> > mvn:groupId/artifactId/version > </configfile> > > Regards > JB > > > On 12/05/2013 01:49 PM, Marco wrote: > >> Hi Ryan, >> thank you very much for your help. >> >> So I'm assuming that there is no real difference in using <configFile> to >> deploy *.cfg or *.properties file, right? >> >> In addition to that, can you please clarify to me if it is possible, in >> any >> way, to include some non-OSGi lib to deploy on /lib folder, only by >> feature? >> The goal is to have some custom libraries in /lib and customize >> system.extra.packages , all by feature without using a custom >> distribution. >> >> Thank you very much. >> Marco >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble. >> com/Config-in-features-xml-to-config-file-tp4030504p4030557.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
