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 2015/10/01 22:35:28 UTC

[jira] [Commented] (SLING-4824) Embed all needed classes in the sling-mock-oak jar

    [ https://issues.apache.org/jira/browse/SLING-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940373#comment-14940373 ] 

Stefan Seifert commented on SLING-4824:
---------------------------------------

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-oak, 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-oak jar
> --------------------------------------------------
>
>                 Key: SLING-4824
>                 URL: https://issues.apache.org/jira/browse/SLING-4824
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Testing Sling Mock Oak 1.0.0
>
>
> When using the JCR_OAK resource resolve type recent versions of the Jackrabbit/Oak 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)