[
https://issues.apache.org/jira/browse/SLING-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-10046.
------------------------------------
Resolution: Fixed
https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/38b629f4531eca18c6ec3428ac693c9bdcd98888
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/0b279088c2c5ceae554691c2ef8f3339a04de1c2
https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/commit/ae89a53468c933ebbd20750a9dad26bee4328cdd
> osgi-mock, sling-mock: Switch to individual OSGi artifacts and compile scope
> ----------------------------------------------------------------------------
>
> Key: SLING-10046
> URL: https://issues.apache.org/jira/browse/SLING-10046
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock Oak 3.0.0-1.16.0, Testing OSGi Mock
> 3.0.0, Testing Sling Mock 3.0.0
>
>
> goal:
> * do no longer depend on the "aggregated OSGi artifacts" {{osgi.core}},
> {{osgi.cmpn}}
> * instead depend on the individual artifacts {{org.osgi.framework}},
> {{org.osgi.service.component}} etc. as required
> * use the version of each osgi artifact that matches the version in run time
> of the project under test
> additionally we want to switch these dependencies to compile scope, so they
> get inherited in the test scope of the projects under test.
> (i assume the structure/naming osgi artifacts has now reached stable state
> after all those changes in the last years)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)