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/07/21 15:59:31 UTC
[jira] Created: (FELIX-638) OBR resolution process does not
consider capability namespace
OBR resolution process does not consider capability namespace
-------------------------------------------------------------
Key: FELIX-638
URL: https://issues.apache.org/jira/browse/FELIX-638
Project: Felix
Issue Type: Bug
Components: Bundle Repository (OBR)
Reporter: Richard S. Hall
Assignee: Richard S. Hall
Originally, capabilities/requirements did not have a namespace; instead, the namespace was just another property to be filtered. It was later separated out because Peter Kriens thought it made more sense this way. Unfortunately, it appears that the resolution process did not get updated to check the separate namespace. This hasn't caused any major issues since we don't have namespace overlap yet, but it should be resolved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-638) OBR resolution process does not consider
capability namespace
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-638.
---------------------------------
Resolution: Fixed
I applied a simple patch to fix this. I will close this issue for now, but I didn't do significant testing.
> OBR resolution process does not consider capability namespace
> -------------------------------------------------------------
>
> Key: FELIX-638
> URL: https://issues.apache.org/jira/browse/FELIX-638
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
>
> Originally, capabilities/requirements did not have a namespace; instead, the namespace was just another property to be filtered. It was later separated out because Peter Kriens thought it made more sense this way. Unfortunately, it appears that the resolution process did not get updated to check the separate namespace. This hasn't caused any major issues since we don't have namespace overlap yet, but it should be resolved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-638) OBR resolution process does not
consider capability namespace
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-638:
------------------------------------
Fix Version/s: bundlerepository-1.0.6
> OBR resolution process does not consider capability namespace
> -------------------------------------------------------------
>
> Key: FELIX-638
> URL: https://issues.apache.org/jira/browse/FELIX-638
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: bundlerepository-1.0.6
>
>
> Originally, capabilities/requirements did not have a namespace; instead, the namespace was just another property to be filtered. It was later separated out because Peter Kriens thought it made more sense this way. Unfortunately, it appears that the resolution process did not get updated to check the separate namespace. This hasn't caused any major issues since we don't have namespace overlap yet, but it should be resolved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.