Details
Description
if a content package is downloaded via CRX package manager it usually also contains intermediate note definitions up to the root node in the jcr_root folder.
the nodetype validator added recently complains about this root node definition which is included by default:
[ERROR] ValidationViolation: "jackrabbit-nodetypes: Node '{http://www.jcp.org/jcr/1.0}root [rep:root (rep:AccessControllable, rep:RepoAccessControllable)]' is not allowed as child of not contained node with potential default types '[nt:folder]': Could not find matching child node definition in parent's node type", filePath=jcr_root\.content.xml, nodePath=/, line=6, column=33
[ERROR] ValidationViolation: "jackrabbit-nodetypes: Mandatory child node missing: jcr:system [rep:system]", filePath=jcr_root\.content.xml, nodePath=/, line=6, column=33
as a workaround i could remove the .content.xml file from the jcr_root folder, but i prefer to keep exactly the content that is contained in the content package.
with this AEM sample project it is possible to reproduce the problem:
https://github.com/stefanseifert/filevault-package-maven-plugin-validation-issues/tree/master/content-packages/conf-content
https://github.com/stefanseifert/filevault-package-maven-plugin-validation-issues/tree/master/content-packages/sample-content
Attachments
Issue Links
- causes
-
JCRVLT-480 NPE when validating not allowed properties
-
- Resolved
-
- is caused by
-
JCRVLT-426 Add nodetype validator
-
- Closed
-
- links to