You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/11/10 10:43:00 UTC

[jira] [Commented] (JCRVLT-731) Filevault validation parent node type defaults to nt:folder, but could in reality be another node type

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

Konrad Windszus commented on JCRVLT-731:
----------------------------------------

I think this idea kind of duplicates JCRVLT-619, isn't it?

> Filevault validation parent node type defaults to nt:folder, but could in reality be another node type
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-731
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-731
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: package maven plugin, Packaging, validation
>    Affects Versions: package-maven-plugin-1.3.4, 3.7.2
>            Reporter: Henry Kuijpers
>            Priority: Major
>
> When creating a filter.xml and using its nodetype-validator, a default nodetype can be configured in case it cannot be found. The default for this is `nt:folder`, but it's possible to provide another default nodetype. Setting that to `sling:Folder` does not necessarily solve all problems, since many parent nodes could actually be something else, maybe even nt:folder, which is very restrictive.
> In other words: It would be nice to be able to feed the nodetypes-validation a set of paths with their respective jcr:primaryType, so that they can be considered by the filevault validation.
> It can be a simple maven-property, which can have key/value-pairs. 
> But maybe we would like to go a few steps further and create the possibility of having those paths and types defined in an external dependency, much like the "tccl"-statements allow to do. 
> Then, it would be possible to create these files per product version (i.e. AEM service pack versions or similar).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)