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/10/02 11:31:00 UTC

[jira] [Commented] (JCRVLT-345) Support pluggable node/file/filter validators

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

Konrad Windszus commented on JCRVLT-345:
----------------------------------------

The validator framework has been committed in https://svn.apache.org/r1867884.

> 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
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 3.4.2, package-maven-plugin-1.0.5
>
>
> 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
(v8.3.4#803005)