karaf-issues mailing list archives

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

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

Vratko Polak commented on KARAF-3901:
-------------------------------------

> it will uninstall the transitive features not used anymore

Oh, I did not get that from
https://karaf.apache.org/manual/latest/users-guide/provisioning.html
"The features resolver is involved during feature uninstallation: transitive features installed
by the uninstalled feature can be uninstalled
themselves if not used by other feature."
I undestood the "can be uninstalled themselves if" part roughly as "are available for user
to manually uninstall only if". I blame my poor English skills.

Anyway, please give me some time to play with Karaf 4 to see whether it already does everything
I want it to.

> 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
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)

Mime
View raw message