[jira] [Commented] (OAK-168) Basic JCR VersionManager support

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger commented on OAK-168:
--------------------------------------

OAK-999 describes backwards compatibility issues with the way how Oak handles OPV copy of non-referenceable nodes. The fix for OAK-999 changes the behavior and the version storage model in Oak is now closer again to Jackrabbit.
                
> Basic JCR VersionManager support
> --------------------------------
>
>                 Key: OAK-168
>                 URL: https://issues.apache.org/jira/browse/OAK-168
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jcr
>            Reporter: Jukka Zitting
>            Assignee: Marcel Reutegger
>
> Versioning is a highly useful feature for many applications, so we definitely should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that simply implements checkin operations by copying content from a node to the respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an operation directly in the Oak API, or if a separate versioning plugin and an associated validator for changes in the {{/jcr:system/jcr:versionStorage}} subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning features.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira