Hi Björn, thank your for your support.
One of the most important reasons to choose Karaf was in fact the feature-management with the option to uninstall/install features (bundles) even on a fully running instance (and it really works). The complete re-install was never an option for us, because actually with 300+ installations there are still around 10 percent of the instances in the WAN which or only connected by ISDN or DSL-light (128kB). With a cache-directory (alone) of 130-150MB it would take days to rollout an update. Btw.: Do you have only standard configurations for the installations or how do you manage the existing configurations somehow (apart from backing up .../bundles/5/*) We started writing a tool that saves the configuration by reading them via jmx and packing them into a single zip. But that is not an ideal solution in all cases. So we are thinking about a shell-extension for backing up and restoring configurations. This would for example provide a way to upgrade an existing karaf-instance to a new Version (as karaf-3 is knocking at the door). Best regards, Uwe. Björn Bength wrote > > +1 > Uninstalling dependent features is a feature we also reeeally need some > times. > Now, most of our deployments and provisioning starts by simply removing > karaf from disk completely and start fresh with unzipping a new copy. > Or simply removing the data directory and start over. > Regards > Björn > -- View this message in context: http://karaf.922171.n3.nabble.com/DISCUSS-Extensions-to-features-tp3536881p3538529.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
