You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Vratko Polak (JIRA)" <ji...@apache.org> on 2015/08/05 10:17:04 UTC
[jira] [Resolved] (KARAF-3901) Automatic Lifecycle of features
[ https://issues.apache.org/jira/browse/KARAF-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vratko Polak resolved KARAF-3901.
---------------------------------
Resolution: Invalid
> Automatic Lifecycle of features
> -------------------------------
>
> Key: KARAF-3901
> URL: https://issues.apache.org/jira/browse/KARAF-3901
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Reporter: Vratko Polak
> Priority: Minor
> Attachments: karaf_20150805.txt
>
>
> This is a wish/improvement to support Automatic Lifecycle of features (and bundles and configfiles).
> (Basically the same thing as "aptitude" does for Debian packages.)
> Explicitly installed features would have "manual" installation flag set,
> others (needed as dependencies) will be called "automatic".
> As soon as an automatic feature has no manual ancestor,
> it would be (attempted to get) uninstalled.
> So that "feature:install ${top-level-feature}"
> would install the tree, marking only the top level feature as manual;
> and "feature:uninstall ${top-level-feature}" (perhaps with some switch, such as --uninstall-unused)
> would do what ordinary user expects it to do, namely
> it would remove the top-level feature
> together with (now unused part of) all its dependencies.
> Note that handling of config files would be left to bundles, they should know by themselves when and how to "un-apply" any applied configuration file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)