You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/05/22 21:51:18 UTC

[jira] [Closed] (SLING-4718) osgi-mock: Support OSGi component name different from implementation class

     [ https://issues.apache.org/jira/browse/SLING-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert closed SLING-4718.
---------------------------------

> 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.3.0
>
>
> 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)