[OAK-168] Basic JCR VersionManager support

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.19
• Component/s: jcr
• Assignee: Marcel Reutegger
• Reporter: Jukka Zitting
• Created: 05/Jul/12 12:28
• Updated: 24/Mar/14 13:36
• Resolved: 19/Mar/14 15:22

Description

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.

Issue Links

• blocks: OAK-444 Authorization for the jcr version store
• is blocked by: OAK-930 VersionManager#isCheckedOut throws IllegalStateException

Sub-Tasks

• Node#getVersionHistory fails with UnsupportedRepositoryOperationException: Closed
• VersionManager is never updated: Closed
• VersionManager#getActivity: Resolved
• VersionHistory#removeVersion: Closed
• Restore and OPV INITIALIZE/CALCULATE: Closed
• Implement Merge: Resolved
• Implement Configurations: Resolved