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/22 11:42:00 UTC
[jira] [Updated] (SLING-4827) Embed all needed classes in the
sling-mock-jackrabbit jar
[ https://issues.apache.org/jira/browse/SLING-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-4827:
-----------------------------------
Description:
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.
was:
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.
> 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
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Testing Sling Mock Oak 0.1.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)