[
https://issues.apache.org/jira/browse/SLING-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-4165.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1639791
> OSGi Mock: Fail-fast when calling methods requiring SCR metadata and this is
> not present
> ----------------------------------------------------------------------------------------
>
> Key: SLING-4165
> URL: https://issues.apache.org/jira/browse/SLING-4165
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.0.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: Testing OSGi Mock 1.1.0
>
>
> some features and signature variants of OSGi mocks require SCR metadata to be
> available in the classpath. currently it is ignored silently if they are
> missing and the feature may fail without notice (perhaps leading to NPEs e.g.
> because a dependency is not injected).
> this may lead to strange unit test failes esp. when using IDEs that cannot
> generate SCR metadata via maven plugin, or (like eclipse and m2e) this fails
> sometimes e.g. when refreshing a project without rebuilding it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
