+1
-----Original Message----- From: Guillaume Nodet <gno...@gmail.com> Date: Sat, 21 May 2011 09:55:03 To: <dev@karaf.apache.org> Reply-To: dev@karaf.apache.org Subject: Re: Uninstall of inner features Maybe an easier way would be to track features that have been explicitely installed differently than features than have been selected automatically because they are dependencies. When those dependant features are no longer used by currently installed features, they could be uninstalled automatically. Imho, that would be fully transparent from a user pov (and i think it should be that way). On Sat, May 21, 2011 at 09:38, Ioannis Canellos <ioca...@gmail.com> wrote: >> >> It could be dangerous to uninstall a top level feature which could be used >> in others features. > > > Indeed. This is why I am trying to find a solution around it. To recap > possible solutions: > a) When uninstalling a feature, check if it contains references to other top > level features and for each reference check if it is used and if not > uninstall it. > b) When specifying delcaring a feature reference use an attribute which > would specify the uninstall behavior. > c) Provide the ability to declare top level features that are only > installable as references and not as standalone (what I described as > abstract features). > > > > -- > *Ioannis Canellos* > * > http://iocanel.blogspot.com > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > Apache ServiceMix <http://servicemix.apache.org/> Committer > * > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com Connect at CamelOne May 24-26 The Open Source Integration Conference http://camelone.com/
