[
https://issues.apache.org/jira/browse/KARAF-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174179#comment-15174179
]
Keith Wire commented on KARAF-4356:
-----------------------------------
Digging into the code it did appear to be deliberate. This is a significant
difference from the behavior in Karaf 2.4.x & 3.x. It may be worth adding
something to the release notes about the change so integrators likes CXF and
camel update their feature files appropriately.
I still believe there are some issues / unexpected behavior when attempting to
uninstall from the console or the Felix Webconsole. The features are listed as
"Started" but cannot be uninstalled, it may be more clear if they cannot be
uninstalled if they were in a different state. Also, the Felix webconsole just
throws and exception when you attempt to uninstall a feature that is not
allowed to be uninstalled.
> Unable to uninstall feature that was not directly installed
> -----------------------------------------------------------
>
> Key: KARAF-4356
> URL: https://issues.apache.org/jira/browse/KARAF-4356
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 4.0.4
> Reporter: Keith Wire
> Assignee: Guillaume Nodet
>
> To reproduce do the following:
> unzip apache-karaf-4.0.4
> {code}
> karaf@root()> feature:repo-add cxf 3.1.4
> karaf@root()> feature:install cxf
> karaf@root()> feature:uninstall cxf-transports-jms/3.1.4
> {code}
> The FeatureService will not attempt to uninstall `cxf-transports-jms` because
> it is not in the requirements list. If that feature is installed directly
> (which adds it to the requirements list), and then uninstalled, the bundles
> are still not stopped. The only way to stop the bundles defined within a
> given feature, is to install that feature directly, and no other features
> that refer to it (ie don't install the root `cxf` feature)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
