felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FELIX-4914) Resolution problem with fragments
Date Mon, 08 Jun 2015 09:40:01 GMT

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

Guillaume Nodet reassigned FELIX-4914:

    Assignee: Guillaume Nodet

> Resolution problem with fragments
> ---------------------------------
>                 Key: FELIX-4914
>                 URL: https://issues.apache.org/jira/browse/FELIX-4914
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: framework-5.0.0, resolver-1.2.0
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
> When a fragment has a requirement that can be fulfilled by another fragment, there are
chances that the resolution fail, depending on the order in which fragments are considered.
 The {{Candidates#prepare}} method is not complete, and in some cases, can leave non-wrapped
capabilities in the candidates map, possibly leading to usage constraints problems.
> I have a test case which I'm trying to clean a bit.

This message was sent by Atlassian JIRA

View raw message