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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/12/11 14:08:07 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-168:
---------------------------------

    Fix Version/s:     (was: 0.14)
                   0.15

> 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
>             Fix For: 0.15
>
>
> 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 was sent by Atlassian JIRA
(v6.1.4#6159)