[
https://issues.apache.org/jira/browse/SLING-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940374#comment-14940374
]
Stefan Seifert commented on SLING-4827:
---------------------------------------
Completed: At revision: 1706320
i've removed the embedding of dependency {{org.apache.sling.jcr.resource}} -
this is a transitive dependency of sling-mock and not a dependency of
sling-mock-jackrabbit, so it should not be embedded here. otherwise we have it
twice - once as dependency of sling-mock and once embedded in this jar.
> Embed all needed classes in the sling-mock-jackrabbit jar
> ---------------------------------------------------------
>
> Key: SLING-4827
> URL: https://issues.apache.org/jira/browse/SLING-4827
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock Jackrabbit 0.1.2
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Testing Sling Mock Jackrabbit 1.0.0
>
>
> When using the JCR_JACKRABBIT resource resolver type recent versions of the
> Jackrabbit are pulled in as transitive dependencies. This causes the
> maven-bundle-plugin to generate Import-Version ranges based on the
> dependencies of those artifacts required for the test code, as opposed to the
> the dependencies required by production code.
> Embedding the relevant dependencies in the sling-oak-mock jar should be
> enough to remove this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
