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 2021/01/16 07:28:01 UTC

[jira] [Closed] (SLING-10046) osgi-mock, sling-mock: Switch to individual OSGi artifacts and compile scope

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

Stefan Seifert closed SLING-10046.
----------------------------------

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