[SLING-5460] Allow skipping resource merges in the Sling Resource Merger

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Resource Merger 1.2.10
• Component/s: ResourceResolver
• Assignee: Unassigned
• Reporter: Radu Cotescu
• Created: 27/Jan/16 13:01
• Updated: 10/Feb/16 15:24
• Resolved: 03/Feb/16 07:58

Description

Assuming there are two components A and B, where B inherits / overlays A, either through sling:resourceSuperType or through regular search path overlay, there's no way to define in B that some content trees should not be merged, if B is obtained through the Resource Merger.

A property like sling:skipMerging would make sense, which should be added to the child resource in order for it not to inherit anything from the parent.

Issue Links

• duplicates: SLING-5468 Resource Merger: Provide a way to completely replace the underlying resources