This is an automated email from the ASF dual-hosted git repository. kwin pushed a commit to branch bugfix/SLING-8060 in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-testing-sling-mock.git
commit 4fea9bc79fc152660cdff144929258c742d6baac Author: Konrad Windszus <[email protected]> AuthorDate: Tue Oct 30 18:31:35 2018 +0100 [SLING-8060] declare OSGi dependencies with scope "compile" They are actually needed at test execution time and using "provided" scope may lead to the fact that they are not part of the test classpath of referencing Maven modules. --- core/pom.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/core/pom.xml b/core/pom.xml index 816aa22..dbed118 100644 --- a/core/pom.xml +++ b/core/pom.xml @@ -33,18 +33,20 @@ <name>Apache Sling Testing Sling Mock Core</name> <dependencies> - + <!-- transitive OSGi dependencies of referenced libraries are given as "provided" but they are + actually necessary at test execution time also to a certain extend directly used, therefore + explicitly define with scope "compile" --> <dependency> <groupId>org.osgi</groupId> <artifactId>osgi.core</artifactId> - <scope>provided</scope> + <scope>compile</scope> </dependency> <dependency> <groupId>org.osgi</groupId> <artifactId>osgi.cmpn</artifactId> - <scope>provided</scope> + <scope>compile</scope> </dependency> - + <!-- non OSGi dependencies --> <dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.testing.osgi-mock.core</artifactId>
