[
https://issues.apache.org/jira/browse/SLING-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3927.
-------------------------------------
Resolution: Fixed
Deprecated the service and added a new util class with a static method
> Cleanup / deprecate ResourceMergerService
> -----------------------------------------
>
> Key: SLING-3927
> URL: https://issues.apache.org/jira/browse/SLING-3927
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Merger 1.2.0
>
>
> With the latest addition of the MergedResourcePicker SPI, the current
> ResourceMergerService is more than questionable.
> We should decide what we wanna do with it.
> Maybe deprecate it completely? The only method that makes sense is
> isMergedResource(). However a service for this seems to be overkill, it could
> rather be an utility method like ResourceUtil.isNonExistingResource()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)