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 2008/10/15 22:26:46 UTC

[jira] Created: (FELIX-777) The resolver does not correctly mark attached fragment modules as resolved

The resolver does not correctly mark attached fragment modules as resolved
--------------------------------------------------------------------------

                 Key: FELIX-777
                 URL: https://issues.apache.org/jira/browse/FELIX-777
             Project: Felix
          Issue Type: Bug
          Components: Framework, Specification compliance
    Affects Versions: felix-1.2.1

            Reporter: Richard S. Hall
            Assignee: Richard S. Hall
             Fix For: felix-1.4.0


The resolver was not correctly marking modules of resolved fragments as resolved, although the bundle was correctly marked as resolved. This caused a failure in the TCK.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (FELIX-777) The resolver does not correctly mark attached fragment modules as resolved

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall closed FELIX-777.
---------------------------------

    Resolution: Fixed

I committed a patch for this.

> The resolver does not correctly mark attached fragment modules as resolved
> --------------------------------------------------------------------------
>
>                 Key: FELIX-777
>                 URL: https://issues.apache.org/jira/browse/FELIX-777
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>    Affects Versions: felix-1.2.1

>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: felix-1.4.0
>
>
> The resolver was not correctly marking modules of resolved fragments as resolved, although the bundle was correctly marked as resolved. This caused a failure in the TCK.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.