Hi Timothee, I am happy to review PRs for adding that feature. Not sure if Oak can import versions via sysview, have you tried that? In the worst case a dedicated import handler needs to be added which recreates the versions with JCR API (not sure if that can set certain metadata of the version). It would be nice though if that feature would not depend on Oak impl or API though. However, I would extend the filter.xml with additional attributes both for exporting and importing versions to not rely on internals like the repository location of versions. Konrad
> Am 19.04.2022 um 11:31 schrieb Timothee Maret <[email protected]>: > > > Hi, > > FileVault does not seem to support versions. A resource like cq:Page is > stripped of its versioning properties [0] upon export. Also, the version > storage under /jcr:system/jcr:versionStorage can be exported but not imported > as versioning properties are protected. > > Is this limited by design ? If not, how about including the versioning > properties in the export and using the System View to import them ? > > Regards, > > Timothee > > [0] jcr:predecessors, jcr:baseVersion, jcr:successors, and jcr:versionHistory
