Hi Brad,
see my comments inline:
1. Is there a directive to tell Karaf to run the features installs
individually and not to lump them together?
Why not splitting your feature in features, and then you can do
feature:install ? I'm not sure I understand what you mean ;)
2. Is there any directive to tell Karaf to delete/remove any
configuration files it has installed when it uninstalls the feature
associate it with it?
Not currently (for "security" reason on the config). You can override
the cfg files at install time.
I can create a Jira to add an option to cleanup file based on
<configfile/> finalName.
3. In the past I’ve used the plugin to install .cfg files from my
bundles and there is a directive override=true/false. Does anything
like that exist for the config done directly from the feature?
I guess you mean <config/> element. No, <config/> element is for
ConfigAdmin, it's created at feature install time.
Regards
JB
