[JCRVLT-124] Inconsistent behaviour of ImportMode.MERGE

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 3.1.28
• Component/s: Misc
• Assignee: Tobias Bocanegra
• Reporter: Ilyas Türkben
• Created: 26/Aug/16 13:44
• Updated: 19/May/21 11:34
• Resolved: 19/May/21 11:34

Description

In [0], it is stated that with ImportMode.MERGE option;

Existing content is not modified, i.e. only new content is added and none is deleted or modified.

however in the code [1], it imports the content only “if node is an authorizable or ACL”.
Is it a documentation issue or implementation issue ? Which behavior the customer should expected?

Steps to reproduce are available:

1. Install example-1.zip
2. Install example-2.zip

Expected: apps/i18n/en/example2 should be created
Outcome: Node is not created

[0] - http://jackrabbit.apache.org/filevault/importmode.html

[1] org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler.accept(WorkspaceFilter, Node, String, ArtifactSetImpl)

if (name.length() == 0 || parent.hasNode(name)) {
                if (wspFilter.getImportMode(path) == ImportMode.MERGE) {
                    // do import the content if node is an authorizable or ACL

Issue Links

• duplicates: JCRVLT-255 ImportModes act on file serialization level not on node level
• relates to: JCRVLT-255 ImportModes act on file serialization level not on node level