Actually there is one section in https://github.com/apache/sling/blob/trunk/contrib/extensions/superimposing/README.md#comparison-with-sling-resource-merger <https://github.com/stefanseifert/sling-superimposing#comparison-with-sling-resource-merger> mentioning why both are necessary, but that section only considers the MergingResourcePicker (/mnt/overlay) not the newer OverridingResourcePicker (/mnt/override).
> On 29 Jan 2016, at 11:46, Konrad Windszus <konrad.winds...@netcentric.biz> > wrote: > > Hi, > IMHO the superimposing resource resolver can be deprecated now > (https://issues.apache.org/jira/browse/SLING-1778) as now the overriding > resource merger is available > (https://issues.apache.org/jira/browse/SLING-3657). > Although the latter uses sling:resourceSuperType instead of > sling:superimposeSourcePath everything can be done with the resource merger > and it is even more flexible. > WDYT about removing the bundle > https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/superimposing? > > Konrad
