[
https://issues.apache.org/jira/browse/KARAF-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006875#comment-15006875
]
Michael Taeschner edited comment on KARAF-4116 at 1/6/16 2:50 PM:
------------------------------------------------------------------
Tested on Windows 7
Testcase:
- download and extract apache-karaf:3.0.5
- extract [^local-repo.zip] into karaf base folder
- copy [^features.xml] to /deploy folder
- start container
- via shell: "feature:install console-log"
- check via "la" that bundle "log" and "consoleLog" are active
- via shell: "feature:install blueprint-log"
- check via "la" that the fragment bundle is in "INSTALLED"
- manually refresh "consoleLog" bundle via shell
- check via "la" that fragment is now resolved
Edit:
- renamed feature "log" to "console-log" to allow testing in version 4.0.3
was (Author: mitaes):
Tested on Windows 7
Testcase:
- download and extract apache-karaf:3.0.5
- extract [^local-repo.zip] into karaf base folder
- copy [^features.xml] to /deploy folder
- start container
- via shell: "feature:install console-log"
- check via "la" that bundle "log" and "consoleLog" are active
- via shell: "feature:install blueprint-log"
- check via "la" that the fragment bundle is in "INSTALLED"
- manually refresh "consoleLog" bundle via shell
- check via "la" that fragment is now resolved
> Feature Installation - no Refresh of Fragment-Host bundle upon installation
> of fragment bundle
> ----------------------------------------------------------------------------------------------
>
> Key: KARAF-4116
> URL: https://issues.apache.org/jira/browse/KARAF-4116
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 3.0.4, 3.0.5
> Reporter: Michael Taeschner
> Attachments: features.xml, local-repo.zip
>
>
> There is a regression in feature installation behavior whereas later
> installation of a feature which contains a fragment bundle and references a
> feature providing the fragment-host bundle the fragment-host is not refreshed
> after feature install, causing the fragment to remain in state "INSTALLED".
> Manual "refresh" of host-fragment bundle will resolve the relationship and
> put framgnent into "RESOLVED" state with host:<host-fragment bundle-id>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
