karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-3901) Automatic Lifecycle of features
Date Tue, 04 Aug 2015 16:16:07 GMT

    [ https://issues.apache.org/jira/browse/KARAF-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653897#comment-14653897

Jean-Baptiste Onofré commented on KARAF-3901:

As I said, Karaf 4 features resolver can do that already: it will uninstall the transitive
features not used anymore (by other bundles or features).

> 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
> This is a wish/improvement to support Automatic Lifecycle of features (and bundles and
> (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

View raw message