You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/08/13 14:30:47 UTC

[jira] [Closed] (FELIX-4914) Resolution problem with identity requirements on fragments

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

Carsten Ziegeler closed FELIX-4914.
-----------------------------------

> Resolution problem with identity requirements on 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
>             Fix For: framework-5.0.1, resolver-1.4.0
>
>
> 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
(v6.3.4#6332)