[
https://issues.apache.org/jira/browse/SLING-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868223#comment-15868223
]
Stefan Seifert commented on SLING-6521:
---------------------------------------
well, it is not incompatible with latest sling-mock version - we're using it in
combination without problems.
but you're right it may lead to subtle problems having this old osgi artifact
id exported as transitive dependency which might get mixed up with the newer
versions.
with the chosen version 4.1.0 no artifact with {{osgi.cmpn}} artifact id
exists, only for newer versions. we may not want to update the osgi dependency
to no force all projects using this mock to update as well.
my proposal is to just declare this dependency as "provided" and let the using
project decide itself which osgi dependency is imported, as long as it is not a
version < 4.1.0.
> Testing Resource Resolver Mock depends on old osgi compendium artifactId
> ------------------------------------------------------------------------
>
> Key: SLING-6521
> URL: https://issues.apache.org/jira/browse/SLING-6521
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing ResourceResolver Mock 1.1.16
> Reporter: Vincent VL
>
> <dependency>
> <groupId>org.osgi</groupId>
> <artifactId>org.osgi.compendium</artifactId>
> <scope>compile</scope>
> </dependency>
> shouldn't this become?
> <dependency>
> <groupId>org.osgi</groupId>
> <artifactId>osgi.cmpn</artifactId>
> <scope>compile</scope>
> </dependency>
> otherwise it is not compatible with the latest sling-mocks version
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
