You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/06/25 17:36:42 UTC

[jira] [Created] (OAK-151) Merge oak-it-jcr to oak-jcr

Jukka Zitting created OAK-151:
---------------------------------

             Summary: Merge oak-it-jcr to oak-jcr
                 Key: OAK-151
                 URL: https://issues.apache.org/jira/browse/OAK-151
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: it, jcr
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting


I originally created the separate oak-it-jcr test component with the assumption that it would otherwise be difficult to separate potentially lengthy JCR integration tests with faster unit tests in oak-jcr. However, our current failsafe plugin setup makes that quite easy, so there's no big need for the separate oak-it-jcr component.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OAK-151) Merge oak-it-jcr to oak-jcr

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OAK-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved OAK-151.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.3

Done in revision 1353621.
                
> Merge oak-it-jcr to oak-jcr
> ---------------------------
>
>                 Key: OAK-151
>                 URL: https://issues.apache.org/jira/browse/OAK-151
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: it, jcr
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.3
>
>
> I originally created the separate oak-it-jcr test component with the assumption that it would otherwise be difficult to separate potentially lengthy JCR integration tests with faster unit tests in oak-jcr. However, our current failsafe plugin setup makes that quite easy, so there's no big need for the separate oak-it-jcr component.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira