jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (JCRVLT-462) Nodetype validator complains about root node
Date Thu, 15 Oct 2020 06:58:00 GMT

    [ https://issues.apache.org/jira/browse/JCRVLT-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180613#comment-17180613

Konrad Windszus edited comment on JCRVLT-462 at 10/15/20, 6:57 AM:

Is fixed by https://github.com/apache/jackrabbit-filevault/pull/98. [~sseifert] Can you cross-check?

was (Author: kwin):
PR: https://github.com/apache/jackrabbit-filevault/pull/98/files

> Nodetype validator complains about root node
> --------------------------------------------
>                 Key: JCRVLT-462
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-462
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>    Affects Versions: 3.4.6, package-maven-plugin-1.1.4
>            Reporter: Stefan Seifert
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 3.4.8
> 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:
> {noformat}
> [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,
> [ERROR] ValidationViolation: "jackrabbit-nodetypes: Mandatory child node missing: jcr:system
[rep:system]", filePath=jcr_root\.content.xml, nodePath=/, line=6, column=33
> {noformat}
> 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

This message was sent by Atlassian Jira

View raw message