Julian Reschke created JCRVLT-598:
-------------------------------------
Summary: need IdConflictPolicy compatible with 3.5.0 behavior
Key: JCRVLT-598
URL: https://issues.apache.org/jira/browse/JCRVLT-598
Project: Jackrabbit FileVault
Issue Type: Sub-task
Components: vlt
Affects Versions: 3.5.8
Reporter: Julian Reschke
Currently, according to the documentation
(https://jackrabbit.apache.org/filevault/referenceablenodes.html),
"IdConflictPolicy.FORCE_REMOVE_CONFLICTING_ID" is supposed to behave as 3.5.0
did.
My tests show however that in 3.5.0, when importing a package with two nodes
ith conflicting UUIDs, both nodes were imported (and one of the UUIDs changed).
>From that point of view, CREATE_NEW_ID seems to be closer (but that one
>assigns new UUIDs two *both* nodes).
Proposal: adjust CREATE_NEW_ID behavior to keep assign a new UUID only when
needed (thus preserving it for one of the nodes), and document *that* mode as
compatible to 3.5.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
