You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/12/31 18:16:45 UTC
[jira] Created: (SLING-1911) If the same resource is at different
locations they should be treated as the same resource
If the same resource is at different locations they should be treated as the same resource
------------------------------------------------------------------------------------------
Key: SLING-1911
URL: https://issues.apache.org/jira/browse/SLING-1911
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: Installer Core 3.0.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Installer Core 3.0.2
If e.g. a bundle is in two different location (in the repository), these bundles represent the same resource.
Currently they end up as two different resources which might create unwanted results, e.g. if the bundle is removed from location A while added at location B In this case the bundle might be uninstalled after this operation, but of course it should still be installed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1911) If the same resource is at different
locations they should be treated as the same resource
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1911.
-----------------------------------
> If the same resource is at different locations they should be treated as the same resource
> ------------------------------------------------------------------------------------------
>
> Key: SLING-1911
> URL: https://issues.apache.org/jira/browse/SLING-1911
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.1.0
>
>
> If e.g. a bundle is in two different location (in the repository), these bundles represent the same resource.
> Currently they end up as two different resources which might create unwanted results, e.g. if the bundle is removed from location A while added at location B In this case the bundle might be uninstalled after this operation, but of course it should still be installed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1911) If the same resource is at different
locations they should be treated as the same resource
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1911.
-------------------------------------
Resolution: Fixed
Fixed in revision 1054158 by using an own comparator for the tree map: the tree map uses Comparable which is special implemented for our resources
> If the same resource is at different locations they should be treated as the same resource
> ------------------------------------------------------------------------------------------
>
> Key: SLING-1911
> URL: https://issues.apache.org/jira/browse/SLING-1911
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.0.2
>
>
> If e.g. a bundle is in two different location (in the repository), these bundles represent the same resource.
> Currently they end up as two different resources which might create unwanted results, e.g. if the bundle is removed from location A while added at location B In this case the bundle might be uninstalled after this operation, but of course it should still be installed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.