[
https://issues.apache.org/jira/browse/SLING-12472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896023#comment-17896023
]
Stefan Seifert commented on SLING-12472:
----------------------------------------
yes, that's part of
https://github.com/apache/sling-org-apache-sling-models-impl/pull/60
> Sling Models Impl: Injector and Implementation Picker service ranking must be
> reversed
> --------------------------------------------------------------------------------------
>
> Key: SLING-12472
> URL: https://issues.apache.org/jira/browse/SLING-12472
> Project: Sling
> Issue Type: Task
> Components: Sling Models
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Critical
>
> SLING-12374 switched the handling of registering multiple implementation
> pickers from "manual" via "RankedServices" to a more elegant pure DS
> solution. but this change introduced a severe bug:
> for historic/backward compatibility reasons, service ranking is interpreted
> "the wrong way" when registering implementation pickers, with highest ranking
> value = lowest ranking. lot of projects depend on this current behavior of
> sling models impl 1.7.0 and below.
> with 1.7.2 and the change from SLING-12374 this is reversed. this needs to be
> fixed to restore the previous behavior.
> Update: the ordering Injector implementation is affected in the same way
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
