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] [Updated] (KARAF-3901) Automatic Lifecycle of features
Date Wed, 05 Aug 2015 08:14:05 GMT

     [ https://issues.apache.org/jira/browse/KARAF-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vratko Polak updated KARAF-3901:
    Attachment: karaf_20150805.txt

So, in Karaf 4 it already works, the "manual" flag is called "Required".
My only remaining issues are very minor:
feature:uninstall --help does not mention it uninstalls non-required dependencies,
and feature:install has --no-auto-manage option, but I did not spot any difference when using

Overall, this issue can be closed.

Copy of console interaction attached; it shows installation and un-installation of "connector"
feature, showcasing that its dependency feature "transaction" is un-installed automatically.

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