Hi JB, the issue is that FileInstall automatically generates a bundle (pax tinybundles?!) from any sub-directory it finds within the declared folder it listens on. As we have an established config structure with ConfigAdmin relevant .cfg in the root folder I get a number of dummy bundles in the container.
Cheers, Michael 2014-11-24 17:15 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > Hi Michael, > > I remember that I did something around this (as we had an issue with our > custom distribution, as a workaround, we just renamed the .cfg file as > .properties, and fileinstall ignores it). > > Let me check and get back to you. > > Regards > JB > > > On 11/24/2014 03:51 PM, Michael Täschner wrote: > >> Hi, >> >> I have an issue with the current fileInstall version inside Karaf. I >> configured additional directories to look for configuration files >> (filefilter = .\\*.cfg) which may also contain folders with other >> configuration files not managed via ConfigAdmin. Unfortunately >> FileInstall interprets these subfolders as exploded bundles. >> >> Is there any way to disable the exploded bundles option ? >> >> Current config (etc/org.apache.felix.fileinstall-isb.cfg): >> # >> # FileMonitor properties >> # >> >> # based on etc/config.properties >> felix.fileinstall.dir = ${karaf.base}/config >> felix.fileinstall.filter = .*\\.cfg >> # default poll = 2000 >> felix.fileinstall.poll = 5000 >> #felix.fileinstall.noInitialDelay = true >> felix.fileinstall.log.level = 3 >> felix.fileinstall.active.level = 50 >> felix.fileinstall.bundles.new.start=false >> >> >> Best Regards, >> Michael >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
