Thanks folks, yes I saw that part of the documentation, which is why I asked the question -- it indicates you can specify a config file, but it sounded like it might be a special case. I wasn't sure I could use it for a general purpose config file rather than specifying where the config file had to go with the "finalname" attribute. Looking at the provisioning schema, it looks like the finalname is required, so I wasn't sure how to specify that this config file was for this particular bundle -- how do I specify the final name for just a standard bundle. I certainly don't want to have to change the config file into a list of properties.
-- View this message in context: http://karaf.922171.n3.nabble.com/Convert-Virgo-PLAN-to-Karaf-Feature-files-tp3867950p3868374.html Sent from the Karaf - User mailing list archive at Nabble.com.
