You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/06/19 16:19:00 UTC

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

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

Robert Munteanu resolved SLING-4824.
------------------------------------
    Resolution: Fixed

Fixed in https://svn.apache.org/r1686422

> Embed all needed classes in the sling-oak-mock 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 0.1.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)