Major 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.
Attachments
Issue Links
1.
|
Node#getVersionHistory fails with UnsupportedRepositoryOperationException |
|
Closed | Marcel Reutegger |
2.
|
VersionManager is never updated |
|
Closed | Marcel Reutegger |
3.
|
VersionManager#getActivity |
|
Resolved | Unassigned |
4.
|
VersionHistory#removeVersion |
|
Closed | Alex Deparvu |
5.
|
Restore and OPV INITIALIZE/CALCULATE |
|
Closed | Marcel Reutegger |
6.
|
Implement Merge |
|
Resolved | Unassigned |
7.
|
Implement Configurations |
|
Resolved | Unassigned |