You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/07/15 18:59:00 UTC

[jira] [Commented] (FELIX-3043) [Framework] Resolver is not correctly resolving fragments in all cases

    [ https://issues.apache.org/jira/browse/FELIX-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066070#comment-13066070 ] 

Richard S. Hall commented on FELIX-3043:
----------------------------------------

I've committed a fix for this that appears to work, but I am not completely satisfied with it. I'll leave this issue open for now.

> [Framework] Resolver is not correctly resolving fragments in all cases
> ----------------------------------------------------------------------
>
>                 Key: FELIX-3043
>                 URL: https://issues.apache.org/jira/browse/FELIX-3043
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>    Affects Versions: framework-3.2.2
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-4.0.0
>
>
> The algorithm to merge fragments into hosts is not always correct when merging fragments into multiple hosts when there are dependencies among the resulting merged hosts. The current algorithm needs to be modified to keep the dependents list up to date in Candidates so that every merged cap/req gets replaced by the corresponding wrapped cap/req from the synthesized merged host module.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira