[
https://issues.apache.org/jira/browse/SLING-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574438#comment-14574438
]
Stefan Seifert commented on SLING-4779:
---------------------------------------
i would love to - but we have to keep in mind that this inserts a strong
dependency on this very new commons osgi version that is not even available in
AEM 6.1 released some days ago.
initially one of the USPs of sling models was "no deps, you can even deploy it
on instance running very old sling versions".
upgrading sling commons OSGI version i a complex sling application is no
problem - but nearly all other bundles depend on it, so it still leaves one
wondering if it is safe to do so.
so the question is if this change is worth the deployment dependency
problematics it will produce. i would recommend to delay this switch for at
least one yer.
> Rely on RankedServices for Sling Models
> ---------------------------------------
>
> Key: SLING-4779
> URL: https://issues.apache.org/jira/browse/SLING-4779
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Konrad Windszus
> Fix For: Sling Models Impl 1.2.0
>
>
> To prevent issues like SLING-4195 and SLING-4192 and to make the code cleaner
> and leaner we should switch to the helper class {{ServiceRanking}} from
> SLING-4521.
> For that we must increase the dependency towards {{commons-osgi}} to version
> 2.3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
