[
https://issues.apache.org/jira/browse/SLING-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688345#comment-17688345
]
Radu Cotescu edited comment on SLING-11774 at 2/14/23 7:46 AM:
---------------------------------------------------------------
Ha, yes! It's the same issue. But there's a bit more to it - in addition to
that, when the migration was done, only the configuration properties were
passed to the pickers. Before we were also passing the registration properties
from the ServiceReference.
was (Author: radu.cotescu):
Ha, yes! It's the same issue. But there's a bit more to it - in addition to
that, when the migration was done, only the configuration properties were
passed to the pickers. Before we were also passing the registration properties
from the ServiceReference. Anyways, let's continue in SLING-11773.
> Fix the registration of the MergedResourcePicker2 implementations
> -----------------------------------------------------------------
>
> Key: SLING-11774
> URL: https://issues.apache.org/jira/browse/SLING-11774
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Resource Merger 1.4.0
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Resource Merger 1.4.2
>
>
> It seems the improvement from SLING-10168 introduced a subtle bug, where the
> components are registered only based on configuration properties, completely
> ignoring their default configuration (where applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
