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 2010/12/13 15:34:00 UTC
[jira] Created: (FELIX-2725) [Framework] Resolver is not correctly
calculating exported packages for already resolved modules
[Framework] Resolver is not correctly calculating exported packages for already resolved modules
------------------------------------------------------------------------------------------------
Key: FELIX-2725
URL: https://issues.apache.org/jira/browse/FELIX-2725
Project: Felix
Issue Type: Bug
Components: Framework, Specification compliance
Affects Versions: framework-3.0.6, framework-3.0.5, framework-3.0.4, framework-3.0.3, framework-3.0.2, framework-3.0.1, framework-3.0.0
Reporter: Richard S. Hall
Fix For: framework-3.2.0
When calculating the package spaces for modules to check for class space consistency, the resolver algorithm incorrectly assumes that already resolved modules with substitutable exports will be handled in import calculation like they are for resolving modules, but already exported modules do not have entries in the candidate map so this fails. As a result, all substitutable exports are dropped and are not considered at all when it comes to consistency checking. We need to look at the wires to calculate exported packages for already resolved modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2725) [Framework] Resolver is not correctly
calculating exported packages for already resolved modules
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-2725.
----------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
> [Framework] Resolver is not correctly calculating exported packages for already resolved modules
> ------------------------------------------------------------------------------------------------
>
> Key: FELIX-2725
> URL: https://issues.apache.org/jira/browse/FELIX-2725
> Project: Felix
> Issue Type: Bug
> Components: Framework, Specification compliance
> Affects Versions: framework-3.0.0, framework-3.0.1, framework-3.0.2, framework-3.0.3, framework-3.0.4, framework-3.0.5, framework-3.0.6
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-3.2.0
>
>
> When calculating the package spaces for modules to check for class space consistency, the resolver algorithm incorrectly assumes that already resolved modules with substitutable exports will be handled in import calculation like they are for resolving modules, but already exported modules do not have entries in the candidate map so this fails. As a result, all substitutable exports are dropped and are not considered at all when it comes to consistency checking. We need to look at the wires to calculate exported packages for already resolved modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2725) [Framework] Resolver is not
correctly calculating exported packages for already resolved modules
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971685#action_12971685 ]
Richard S. Hall commented on FELIX-2725:
----------------------------------------
Patch has been applied.
> [Framework] Resolver is not correctly calculating exported packages for already resolved modules
> ------------------------------------------------------------------------------------------------
>
> Key: FELIX-2725
> URL: https://issues.apache.org/jira/browse/FELIX-2725
> Project: Felix
> Issue Type: Bug
> Components: Framework, Specification compliance
> Affects Versions: framework-3.0.0, framework-3.0.1, framework-3.0.2, framework-3.0.3, framework-3.0.4, framework-3.0.5, framework-3.0.6
> Reporter: Richard S. Hall
> Fix For: framework-3.2.0
>
>
> When calculating the package spaces for modules to check for class space consistency, the resolver algorithm incorrectly assumes that already resolved modules with substitutable exports will be handled in import calculation like they are for resolving modules, but already exported modules do not have entries in the candidate map so this fails. As a result, all substitutable exports are dropped and are not considered at all when it comes to consistency checking. We need to look at the wires to calculate exported packages for already resolved modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2725) [Framework] Resolver is not correctly
calculating exported packages for already resolved modules
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall updated FELIX-2725:
-----------------------------------
Fix Version/s: (was: framework-3.2.0)
framework-3.0.7
> [Framework] Resolver is not correctly calculating exported packages for already resolved modules
> ------------------------------------------------------------------------------------------------
>
> Key: FELIX-2725
> URL: https://issues.apache.org/jira/browse/FELIX-2725
> Project: Felix
> Issue Type: Bug
> Components: Framework, Specification compliance
> Affects Versions: framework-3.0.0, framework-3.0.1, framework-3.0.2, framework-3.0.3, framework-3.0.4, framework-3.0.5, framework-3.0.6
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-3.0.7
>
>
> When calculating the package spaces for modules to check for class space consistency, the resolver algorithm incorrectly assumes that already resolved modules with substitutable exports will be handled in import calculation like they are for resolving modules, but already exported modules do not have entries in the candidate map so this fails. As a result, all substitutable exports are dropped and are not considered at all when it comes to consistency checking. We need to look at the wires to calculate exported packages for already resolved modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.