You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/11/27 11:33:35 UTC

[jira] [Commented] (OAK-14) Identify and document changes in behaviour wrt. Jackrabbit 2

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

Bertrand Delacretaz commented on OAK-14:
----------------------------------------

FWIW a while ago I created a test module in Sling, that runs the exact same tests on a Jackrabbit repository and then on Oak [1].

I'd be open to giving Oak committers write access to that module (if the Sling PMC accepts) if you guys think it's useful.

[1] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/it-jackrabbit-oak/

> Identify and document changes in behaviour wrt. Jackrabbit 2
> ------------------------------------------------------------
>
>                 Key: OAK-14
>                 URL: https://issues.apache.org/jira/browse/OAK-14
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, doc, jcr
>            Reporter: Michael Dürig
>              Labels: compatibility, documentation, test
>             Fix For: 0.15
>
>
> Some implementation specific behaviour will likely change. We should document the cases, provide test cases and migration paths where applicable. 
> This issue serves as a container. Please create separate issues for each identifies change in behaviour.



--
This message was sent by Atlassian JIRA
(v6.1#6144)