[JCRVLT-415] jackrabbit-emptyelements validator reports error for nested folders

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4.2
• Fix Version/s: 3.4.4, package-maven-plugin-1.1.2
• Component/s: vlt
• Assignee: Konrad Windszus
• Reporter: Csaba Varga
• Created: 25/Feb/20 12:31
• Updated: 23/Mar/23 18:24
• Resolved: 06/Mar/20 07:28

Description

When an nt:folder node is present under an orderable node, the "jackrabbit-emptyelements" validator will report an issue (breaking the build with the default settings of the package Maven plugin). I believe this shouldn't be reported as an issue because the AEM Package Manager can generate packages like this. For example, see the attached test.zip file, which was exported on an out-of-the-box AEM 6.5 instance with dummy nodes.

To reproduce, save test.zip somewhere, then invoke the validation Maven goal in the command like like this:

mvn org.apache.jackrabbit:filevault-package-maven-plugin:validate-package -Dvault.packageToValidate=test.zip

test.zip contains the following very simple node hierarchy:

/
  test (nt:unstructured)
    foo (nt:folder)
      bar (nt:folder)
        baz (sling:OrderedFolder)

The error I'm getting is:

[ERROR] ValidationViolation: "jackrabbit-emptyelements: Found empty nodes: '/test/foo' (in 'test\.content.xml') (used for ordering only) which are included in the filter with mode=merge. Rather use the according include/exclude patterns."

Issue Links

• causes: JCRVLT-542 FolderArtifactHandler not respecting ImportMode on adjusting primaryTypes
• is related to: SLING-11809 Disable "overwritePrimaryTypesOfFolders" in the distribution journal
• is related to: JCRVLT-557 Breaking change in behavior for implict nodetype calculation
• relates to: JCRVLT-251 Child nodes mentioned in parent node's docview xml are not cleared correctly during installation
• links to: Github PR