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

Konrad Windszus commented on JCRVLT-423:
----------------------------------------

What about considering the namespace definitions from the contained 
{{nodetypes.cnd}} in the pacage. I think there is a high chance, that the 
namespace is defined in there (although it may be that the namespace is only 
used in node names/property names without being used in any node type).

> filevault-package-maven-plugin 1.1.2: Validation fails on /content/cq:tags 
> node
> -------------------------------------------------------------------------------
>
>                 Key: JCRVLT-423
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-423
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.1.2
>            Reporter: Stefan Seifert
>            Priority: Major
>
> i've encountered another problem, occurs on 1.1.2 and 1.1.3-SNAPSHOT, not 
> with version 1.1.0 of the plugin.
> sample project that contains some content below {{/content/cq:tags}}:
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.1.2-validation-issues/tree/master/content-packages/sample-content
> leads to validation failures:
> {noformat}
> [ERROR] ValidationViolation: "jackrabbit-docviewparser: Invalid XML found: 
> Given root node name 'cq:tags' (implicitly given via filename) cannot be 
> resolved. The prefix used in the filename must be declared as XML namespace 
> in the child docview XML as well!", 
> filePath=jcr_root\content\_cq_tags\.content.xml
> [ERROR] ValidationViolation: "jackrabbit-filter: Node 
> '/content/cq:tags/.content.xml' is not contained in any of the filter rules", 
> filePath=jcr_root\content\_cq_tags\.content.xml
> {noformat}
> the package content is exactly that what the package manager produced when 
> downloading the package, so the package data itself is correct.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to