Hi, the filevault-package-maven-plugin validates if a package contains a new index definition. This behaviour can be disabled via the "allowIndexDefinitions" parameter (https://jackrabbit.apache.org/filevault-package-maven-plugin/generate-metadata-mojo.html#allowIndexDefinitions) . There was a bug recently reported about that at https://issues.apache.org/jira/browse/JCRVLT-343?focusedCommentId=16891508&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16891508 because there was a rep:policy node modified below oak:index. It is not 100% clear under which circumstances the validation should fail: a) only for synchronous index definition nodes b) for all index node definitions c) for all changes below /oak:index
I tend to say actually only a) might lead to issues and therefore only those nodes should make the build optionally fail. WDYT? Thanks, Konrad
