Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F1B818CA7 for ; Wed, 6 Jan 2016 13:25:40 +0000 (UTC) Received: (qmail 48486 invoked by uid 500); 6 Jan 2016 13:25:40 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 48450 invoked by uid 500); 6 Jan 2016 13:25:40 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 48413 invoked by uid 99); 6 Jan 2016 13:25:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 13:25:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0EAAF2C14F4 for ; Wed, 6 Jan 2016 13:25:40 +0000 (UTC) Date: Wed, 6 Jan 2016 13:25:40 +0000 (UTC) From: "Michael Taeschner (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 [ https://issues.apache.org/jira/browse/KARAF-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Taeschner updated KARAF-4116: ------------------------------------- Attachment: features.xml > 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: -- This message was sent by Atlassian JIRA (v6.3.4#6332)