karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KARAF-3579) bundles in etc/startup.properties shouldn't be uninstalled through feature service
Date Fri, 13 Mar 2015 08:06:38 GMT

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

Freeman Fang resolved KARAF-3579.
       Resolution: Fixed
    Fix Version/s: 3.0.4

commit fix
http://git-wip-us.apache.org/repos/asf/karaf/commit/ae748e05 for karaf-2.x branch
http://git-wip-us.apache.org/repos/asf/karaf/commit/333f7b2d for karaf-3.0.x branch

> bundles in etc/startup.properties shouldn't be uninstalled through feature service
> ----------------------------------------------------------------------------------
>                 Key: KARAF-3579
>                 URL: https://issues.apache.org/jira/browse/KARAF-3579
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.4.2, 3.0.4
> bundles in etc/startup.properties are very fundamental and are installed before feature
service is available. However, we can always uninstall those critical bundles through feature
service. For an instance, after Karaf container is up, we install karaf-framework feature
and unintall karaf-framework feature, as karaf-framework feature include several bundles from
the etc/startup.properties , so uninstall karaf-framework feature simply cause the container
become malfunction. This shouldn't happen IMO.
> So when the feature service is up, we should register an virtual feature like "startup"
and this feature hold all bundles in startup.properties to ensure those bundles won't be uninstalled
through other features occasionally.

This message was sent by Atlassian JIRA

View raw message