Return-Path: <issues-return-30795-archive-asf-public=cust-asf.ponee.io@karaf.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 24C9D200B6A
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 22 Aug 2016 18:04:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 23AC5160ABC; Mon, 22 Aug 2016 16:04:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 90266160AB3
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 22 Aug 2016 18:04:21 +0200 (CEST)
Received: (qmail 31134 invoked by uid 500); 22 Aug 2016 16:04:20 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 31106 invoked by uid 99); 22 Aug 2016 16:04:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2016 16:04:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id A1C592C014C
	for <issues@karaf.apache.org>; Mon, 22 Aug 2016 16:04:20 +0000 (UTC)
Date: Mon, 22 Aug 2016 16:04:20 +0000 (UTC)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12913355.1447690937000.371905.1471881860659@Atlassian.JIRA>
In-Reply-To: <JIRA.12913355.1447690937000@Atlassian.JIRA>
References: <JIRA.12913355.1447690937000@Atlassian.JIRA> <JIRA.12913355.1447690937214@arcas>
Subject: [jira] [Commented] (KARAF-4116) Feature Installation - no Refresh
 of Fragment-Host bundle upon installation of fragment bundle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 22 Aug 2016 16:04:22 -0000


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

Guillaume Nodet commented on KARAF-4116:
----------------------------------------

The discovery of bundles to refresh is done among the bundles related to the installed feature, so a workaround would be to include the blueprint core bundle in your feature as a dependency.

> 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, 3.0.6
>            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 fragnent into "RESOLVED" state with host:<host-fragment bundle-id>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)