Thanks, it would be great if you created the Jira ticket. I do understand that it's difficult for any of this to be automated from the perspective of Karaf unless one kept a tree of dependencies in memory with reference counting. That would end up with a mark and sweep like garbage collector and that could get very complex. But as you say, if I know that my config is used only by my current feature (pretty common) and should be uninstalled when that feature is uninstalled, then having an override to delete seems reasonable.
For backward compatibility, the default behavior would have to be what it is - do nothing. Only if a user explicitly overrides that behavior and tells it to delete the config would it actually do so. -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
