[
https://issues.apache.org/jira/browse/SLING-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-4718:
----------------------------------
Summary: osgi-mock: Support OSGi component name different from
implementation class (was: osgi-mock: Support OSGi coponent name different
from implementation class)
> osgi-mock: Support OSGi component name different from implementation class
> --------------------------------------------------------------------------
>
> Key: SLING-4718
> URL: https://issues.apache.org/jira/browse/SLING-4718
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.2.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Labels: mocks
> Fix For: Testing OSGi Mock 1.2.2
>
>
> it is possible to define a different component name than the implementation
> class via SCR. the element "implemention" contains the correct implementian
> class name in this case. osgi-mock should support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)