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/05/13 19:04:02 UTC

[jira] [Commented] (SLING-4605) Add support for an Oak resource resolver type mock

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

Stefan Seifert commented on SLING-4605:
---------------------------------------

this should be a different - new - bundle.

the main reason for separating the sling-mocks-jackrabbit from sling-mocks bundle was to avoid including dozens of jackrabbit implementation-related maven dependencies in the developers project (even if only with test scope) if not really required. the same would apply to an oak resource resolver type which has to include all libraries required to run a minimal oak as well.

currently i've now experience setting up a minimal oak instance for a unit test like it is done by {{org.apache.sling.commons.testing.jcr.RepositoryProvider}} which i happily re-used for sling-mock-jackrabbit.

> Add support for an Oak resource resolver type mock
> --------------------------------------------------
>
>                 Key: SLING-4605
>                 URL: https://issues.apache.org/jira/browse/SLING-4605
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing Sling Mock Jackrabbit 0.1.2
>            Reporter: Robert Munteanu
>             Fix For: Testing Sling Mock Jackrabbit 0.1.4
>
>
> As we have Oak support in the launchpad now and there are some internal differences between Oak and Jackrabbit it would be good to be able to test against an Oak repository instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)