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

Carsten Ziegeler updated SLING-3928:
------------------------------------
    Description: 
With having extensible merging strategies through the picker service, all 
merging providers should be disabled by default, including the 
MergedResourceProviderFactory
This is an incompatible change, however as discussed in SLING-3927 the current 
api might be obsolete anyway.

One solution would be to regard the new picker based implementation as a new 
module with a new symbolic name.

  was:
With having extensible merging strategies through the picker service, all 
merging providers should be disabled by default, including the 
MergedResourceProviderFactory
This is an incompatible change, however as discussed in SLING-3908 the current 
api might be obsolete anyway.

One solution would be to regard the new picker based implementation as a new 
module with a new symbolic name.


> Disable MergedResourceProviderFactory by default
> ------------------------------------------------
>
>                 Key: SLING-3928
>                 URL: https://issues.apache.org/jira/browse/SLING-3928
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Carsten Ziegeler
>             Fix For: Resource Merger 1.2.0
>
>
> With having extensible merging strategies through the picker service, all 
> merging providers should be disabled by default, including the 
> MergedResourceProviderFactory
> This is an incompatible change, however as discussed in SLING-3927 the 
> current api might be obsolete anyway.
> One solution would be to regard the new picker based implementation as a new 
> module with a new symbolic name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to