[jira] [Comment Edited] (KARAF-4116) Feature Installation - no Refresh of Fragment-Host bundle upon installation of fragment bundle

["Michael Taeschner (JIRA)" <ji...@apache.org>]

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

Michael Taeschner edited comment on KARAF-4116 at 1/6/16 1:30 PM:
------------------------------------------------------------------

Added "feature" dependency to "blueprint-log" feature to ensure bundles in the feature-tree are looked at for refresh but issue remains. This is to correctly show the issue at hand.

My current dirty workaround is to reference the host bundle as dependency in the fragment bundle feature, as shown below. But in my opinion this is duplicate effort.
{noformat}
<feature name="blueprint-log" version="1.0.0" install="false">
	<feature>log</feature>
	<bundle dependency="true">mvn:org.example.osgi/consoleLog/1.0.0-SNAPSHOT</bundle>		
	<bundle>mvn:org.example.osgi/consoleLog-blueprint/1.0.0-SNAPSHOT</bundle>
</feature>
{noformat}


was (Author: mitaes):
Added "feature" dependency to "blueprint-log" feature to ensure bundles in the feature-tree are looked at for refresh but issue remains. This is to correctly show the issue at hand.

My current dirty workaround is to reference the host bundle as dependency in the fragment bundle feature, as shown below. But in my opinion this is duplicate effort.
{noformat}
<feature name="blueprint-log" version="1.0.0" install="false">
	<feature>log</feature>
	<bundle>mvn:org.example.osgi/consoleLog-blueprint/1.0.0-SNAPSHOT</bundle>
</feature>
{noformat}

> 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, 4.0.3
>            Reporter: Michael Taeschner
>            Priority: Critical
>         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)