[
https://issues.apache.org/jira/browse/JCRVLT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893432#comment-16893432
]
Jörg Hoh commented on JCRVLT-345:
---------------------------------
This function is crucial to the build process, I agree. But I don't understand
why it has to be part of the filevault-package-mp, especially if oakpal already
exists.
> Support pluggable node/file/filter validators
> ---------------------------------------------
>
> Key: JCRVLT-345
> URL: https://issues.apache.org/jira/browse/JCRVLT-345
> Project: Jackrabbit FileVault
> Issue Type: New Feature
> Components: package maven plugin
> Reporter: Konrad Windszus
> Priority: Major
>
> IMHO it would be good to support pluggable node, file and filter.xml
> validators for custom validations:
> The filevault-package-m-p should ship/ships with these ones out of the box
> # check for index definition nodes
> # check for bundles, OSGi configuration and subpackages (in the context of
> JCRVLT-249)
> # check for adherence to the FileVault DocView for .content.xml files
> # check for filter.xml coverage of all nodes/files
> The following ones are just ideas for custom validations:
> # check for usage of deprecated resource types
> # check for content classification
> (https://helpx.adobe.com/experience-manager/6-5/sites/deploying/using/sustainable-upgrades.html)
> An SPI should be defined and allow everyone to come up with validator
> extensions which are automatically executed during the {{package}} goal on
> all files/nodes being included in the package
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
