[
https://issues.apache.org/jira/browse/SLING-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-7794.
-----------------------------------
Resolution: Fixed
thanks for the contribution! - i've applied the PR with a cosmetic modification
https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/dbfffe91d6e2a1b640a19d73cfae62826690129d
> osgi-mock: Dynamic reference properties
> ---------------------------------------
>
> Key: SLING-7794
> URL: https://issues.apache.org/jira/browse/SLING-7794
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing OSGi Mock 2.3.8
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing OSGi Mock 2.3.10
>
>
> [PR
> #3|https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/3]
> from [badfish69|https://github.com/badfish69]:
> {quote}
> This is a pull request to add support for correct resolution of SCR
> references where the target filter is provided via service properties rather
> than being hard-coded into the metadata.
> e.g. if you have code like this
> {code:java}
> @reference
> MyClass myClass
> {code}
> The OSGI spec allows for the target service to be filtered via a property:
> myClass.target, which provides a runtime equivalent to the
> @reference(target=filter) static way of doing it.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
