[ https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916475#comment-13916475 ]
Alexander Klimetschek commented on SLING-2986: ---------------------------------------------- The service is not as designed and mixes different concerns: the API that was removed and which I wanted to have back was added in a totally different way that ties the service to the sling search path use case only. See my mail on the list: http://sling.markmail.org/thread/3wt33wniwgflmk27 and created SLING-3423 > Merged Resource Provider > ------------------------ > > Key: SLING-2986 > URL: https://issues.apache.org/jira/browse/SLING-2986 > Project: Sling > Issue Type: New Feature > Components: Extensions > Reporter: Gilles Knobloch > Assignee: Carsten Ziegeler > Fix For: Resource Merger 1.0.0 > > Attachments: SLING-2986-WithService.zip, SLING-2986.zip > > > As exchanged once with Felix Meschberger, the idea is to implement a custom > resource provider, with ability to merge multiple resources based on your > search paths. > For instance, if your search paths are > /apps > /libs > Hitting /merge/my/resource/is/here will check > /apps/my/resource/is/here > /libs/my/resource/is/here > There are some options like: > - add/override property > - delete a property of the resource under /libs > - reorder nodes if available > I intend to submit this patch as soon as possible. > Code is currently located at https://github.com/gknob/sling-resourcemerger -- This message was sent by Atlassian JIRA (v6.1.5#6160)