You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2014/11/29 16:47:13 UTC

[jira] [Closed] (SLING-3927) Cleanup / deprecate ResourceMergerService

     [ https://issues.apache.org/jira/browse/SLING-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson closed SLING-3927.
---------------------------------

> 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)