[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list

2017-06-16 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
 ] 

Konrad Windszus edited comment on SLING-6956 at 6/16/17 12:56 PM:
--

Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Only one underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should not change the order
{code}
  node1
  node2
  node3
{code}
Some underlying resource being overlaid in a different order
{code}
/libs/p1/components/c1
  node1
  node3
  node5
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
  node3
  node4
{code} should lead to the order from the overlaid resources being kept after 
the non-overlaid resources
{code}
  node1
  node5
  node2
  node3
  node4
{code}



was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Only one underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should not change the order
{code}
  node1
  node2
  node3
{code}
Some underlying resource being overlaid in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should lead to the order from the overlaid resources
{code}
  node1
  node3
  node2
{code}


> Sling Resource Merger: Resources being overlaid are always listed at the end 
> of the list
> 
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed 
> last!
> This is also not desired. Only in case some resources have been added which 
> were not defined by the underlying resource, the order should be changed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list

2017-06-14 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
 ] 

Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:17 PM:
--

Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Only one underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should not change the order
{code}
  node1
  node2
  node3
{code}
Some underlying resource being overlaid in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should lead to the order from the overlaid resources
{code}
  node1
  node3
  node2
{code}



was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Some underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should lead to the same order 
{code}
  node1
  node2
  node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should lead to
{code}
  node1
  node3
  node2
{code}


> Sling Resource Merger: Resources being overlaid are always listed at the end 
> of the list
> 
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed 
> last!
> This is also not desired. Only in case some resources have been added which 
> were not defined by the underlying resource, the order should be changed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list

2017-06-14 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
 ] 

Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:08 PM:
--

Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Some underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should lead to the same order 
{code}
  node1
  node2
  node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should lead to
{code}
  node1
  node3
  node2
{code}



was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Some underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should lead to the same order 
{code}
  node1
  node2
  node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should still lead to
{code}
  node1
  node2
  node3
{code}


> Sling Resource Merger: Resources being overlaid are always listed at the end 
> of the list
> 
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed 
> last!
> This is also not desired. Only in case some resources have been added which 
> were not defined by the underlying resource, the order should be changed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SLING-6956) Sling Resource Merger: Resources being overlaid are always listed at the end of the list

2017-06-14 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049076#comment-16049076
 ] 

Konrad Windszus edited comment on SLING-6956 at 6/14/17 12:03 PM:
--

Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to the new items being added at the end of the list
{code}
  node1
  node2
  node3
  node4
{code}
Some underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should lead to the same order 
{code}
  node1
  node2
  node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should still lead to
{code}
  node1
  node2
  node3
{code}



was (Author: kwin):
Some more examples
Child resource being added by the overlaid resource
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node4
{code} should lead to
{code}
  node1
  node2
  node3
  node4
{code}
Some underlying resources being modified 
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node2
{code} should lead to
{code}
  node1
  node2
  node3
{code}
Some underlying resources being modified in a different order
{code}
/libs/p1/components/c1
  node1
  node2
  node3
/libs/p2/components/c1 (sling:resourceSuperType=/libs/p1/components/c1)
  node3
  node2
{code} should still lead to
{code}
  node1
  node2
  node3
{code}


> Sling Resource Merger: Resources being overlaid are always listed at the end 
> of the list
> 
>
> Key: SLING-6956
> URL: https://issues.apache.org/jira/browse/SLING-6956
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Resource Merger 1.3.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.4
>
>
> Due to the change in SLING-4915, all overlaid resources are now always listed 
> last!
> This is also not desired. Only in case some resources have been added which 
> were not defined by the underlying resource, the order should be changed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)