[
https://issues.apache.org/jira/browse/JCRVLT-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912582#comment-17912582
]
Konrad Windszus commented on JCRVLT-791:
----------------------------------------
None of the API methods exposed by
https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/version/VersionManager.html
allow to create a version in the past with all correct metadata as creating a
version requires a checkin of a regular node. Also checkin-in of a node has
global effect (i.e. would at least temporarily affect all parallel JCR sessions
acting on the same node or one of its children)
> Allow to include node version history in package
> ------------------------------------------------
>
> Key: JCRVLT-791
> URL: https://issues.apache.org/jira/browse/JCRVLT-791
> Project: Jackrabbit FileVault
> Issue Type: New Feature
> Components: Packaging
> Reporter: Konrad Windszus
> Priority: Major
>
> Sometimes one doesn't want to only transfer the current version of a subtree
> but also their history.
> Just including certain paths below {{/jcr:system/jcr:versionStorage}} will
> not work as outlined in
> https://s.apache.org/jcr-2.0-spec/15_Versioning.html#15.10%20Serialization%20of%20Version%20Storage.
> Instead FileVault would need to treat version nodes specially (similar to
> Authorization/User nodes) and would need to leverage special JCR Versioning
> API to restore it.
> In addition the filter parametrization needs to be extended in this regard to
> be able to express how many versions (max) if at all should be included along
> with a serialized node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
