Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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
Attachments
Attachments
Issue Links
- is related to
-
SLING-1778 Symlinks / Superimposing Resources
- Closed
- relates to
-
SLING-3423 ResourceMergerService API must allow custom merge paths
- Closed
- links to