Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Thu, 24 Apr 2014 19:59:20 +0000 (UTC)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12710375.1398360866319.175046.1398369560923@arcas>
In-Reply-To: <JIRA.12710375.1398360866319@arcas>
References: <JIRA.12710375.1398360866319@arcas>
Subject: [jira] [Updated] (FELIX-4495) Candidates from already resolved
 fragments get ignored if no new hosts are available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Richard S. Hall updated FELIX-4495:
-----------------------------------

    Affects Version/s: resolver-1.0.0

> Candidates from already resolved fragments get ignored if no new hosts are available
> ------------------------------------------------------------------------------------
>
>                 Key: FELIX-4495
>                 URL: https://issues.apache.org/jira/browse/FELIX-4495
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: resolver-1.0.0
>            Reporter: Thomas Watson
>             Fix For: resolver-1.2.0
>
>         Attachments: org.apache.felix.resolver.patch
>
>
> org.apache.felix.resolver.Candidates.populateResource(ResolveContext, Resource) gets called for fragments even if they are already resolved so that we can attach them to more hosts as needed.
> The issue is that this method will throw a ResolutionException if the fragment cannot attach to any new hosts during the current resolve process.  This has the effect of removing any candidate capabilities provided by already resolved fragments.


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