Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Tue, 19 Aug 2014 21:15:20 +0000 (UTC)
From: "Thomas Watson (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <JIRA.12735165.1408480955682.36297.1408482920082@arcas>
In-Reply-To: <JIRA.12735165.1408480955682@arcas>
References: <JIRA.12735165.1408480955682@arcas>
Subject: [jira] [Resolved] (ARIES-1237) subsytem BundleEventHook incorrectly
 associating new bundle installs to subsystems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Watson resolved ARIES-1237.
----------------------------------

    Resolution: Fixed

Fixed with:

http://svn.apache.org/viewvc?view=revision&revision=1618991

Thanks!

> subsytem BundleEventHook incorrectly associating new bundle installs to subsystems
> ----------------------------------------------------------------------------------
>
>                 Key: ARIES-1237
>                 URL: https://issues.apache.org/jira/browse/ARIES-1237
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-1.0.1
>         Environment: various
>            Reporter: Samuel Bratton
>             Fix For: subsystem-1.0.1
>
>         Attachments: aries1237.patch
>
>
> BundleEvent hook has logic to detect new bundle installed by an existing bundle context that is a subsystem constituent and make the new bundle a constituent of same susbsystem. It is triggering on budles that are merely dependencies. 
> As a result of this incorrect association, the BundleResolverHook may later incorrectly stop a bundle from resolving by incorrectly associating the "victim" bundle with a subsytem in installing state.


--
This message was sent by Atlassian JIRA
(v6.2#6252)