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 2019/07/25 10:26:00 UTC
[jira] [Created] (JCRVLT-345) Support pluggable node/file/filter
validators
Konrad Windszus created JCRVLT-345:
--------------------------------------
Summary: 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
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)