[
https://issues.apache.org/jira/browse/JCRVLT-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242278#comment-17242278
]
Konrad Windszus commented on JCRVLT-485:
----------------------------------------
The `ignore` specifies the on-parent versioning policy
(https://docs.adobe.com/content/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.7.2.5%20On-Parent-Version)
and has IMHO no relevance for the validation.
Regarding mandatory protected subnodes it seems that they are somehow
automatically created. [~sseifert] can you confirm that those are there after
an import of the attached package? I am still wondering how that happens...
> Validation fails for nodetypes extending mix:versionable
> --------------------------------------------------------
>
> Key: JCRVLT-485
> URL: https://issues.apache.org/jira/browse/JCRVLT-485
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.8
> Reporter: Stefan Seifert
> Priority: Major
>
> when validation a content package containing data with a node type extending
> mix:versionable (and the protected properties are stripped out of the local
> content) validation failes with:
> {noformat}
> ERROR] ValidationViolation: "jackrabbit-nodetypes: Mandatory property
> 'jcr:predecessors' missing in node with types [cq:WorkflowModel] at
> /var/workflow/models/dam/dam_update_asset1"
> [ERROR] ValidationViolation: "jackrabbit-nodetypes: Mandatory property
> 'jcr:baseVersion' missing in node with types [cq:WorkflowModel] at
> /var/workflow/models/dam/dam_update_asset1"
> [ERROR] ValidationViolation: "jackrabbit-nodetypes: Mandatory property
> 'jcr:versionHistory' missing in node with types [cq:WorkflowModel] at
> /var/workflow/models/dam/dam_update_asset1"
> {noformat}
> sample project to reproduce the problem:
> https://github.com/stefanseifert/filevault-package-maven-plugin-validation-issues/tree/master/content-packages/workflow-content
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
