[
https://issues.apache.org/jira/browse/SLING-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049076#comment-16049076
]
Konrad Windszus commented on SLING-6956:
----------------------------------------
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)
