Hello,
this question is not directly associated with Karaf 2.4, but it's a
regression from Karaf 2.3.x : the "felix.fileinstall.filter" properties is
not always applied.
When Karaf start, FileInstall register all bundles installed which location
match the scanner location. After that, these bundles are involved in the
start/stop/refresh check. The bug here is that the search don't apply the
name filter :
Karaf use fileinstall in folder 'etc' with the pattern *.cfg, but
fileinstall register all bundles which location starts with "etc"
("blueprint:file:etc/myfile.xml") and then try to start/refresh this bundle.
If this bundle is registered by another configuration a fileinstall
(folder:"etc", filter:"*.xml", startLevel=90), there is a race condition
between the two scanners and the bundle is sometimes not started.
If i'm not wrong, the correction is simple :
DirectoryWatch.initializeCurrentManagedBundles must check the bundle
location against the filename regex.
I don't know if there is a dedicated mailinglist/forum for
felix.fileinstall, i apologize if it is not the right place..
Regards,
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-2-4-0-and-FileInstall-tp4035601.html
Sent from the Karaf - User mailing list archive at Nabble.com.
