[JCRVLT-345] Support pluggable node/file/filter validators

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.2, package-maven-plugin-1.1.0
• Component/s: package maven plugin
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 25/Jul/19 10:25
• Updated: 15/Jan/20 15:40
• Resolved: 08/Oct/19 15:23

Description

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

1. check for index definition nodes
2. check for bundles, OSGi configuration and subpackages (in the context of JCRVLT-249)
3. check for adherence to the FileVault DocView for .content.xml files
4. check for filter.xml coverage of all nodes/files

The following ones are just ideas for custom validations:

1. check for usage of deprecated resource types
2. 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

Issue Links

• is related to: JCRVLT-357 Split up DocViewSaxImporter: Separate parsing from importing