[
https://issues.apache.org/jira/browse/JCRVLT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891508#comment-16891508
]
Tobias Bocanegra commented on JCRVLT-343:
-----------------------------------------
the original reason for having this check was somewhat along the lines:
{quote}
Oak CFP should not add new index definitions because this could mean that
customers face up to 24 hours down time for reindexing depending on their
repository size. We need an automated check which verifies that there is no new
index definition compared to the GA version.
{quote}
i.e. If you add an index definition into your package, you'd better know what
you are doing.
I'm not sure how oak detects a change in the index definition, and if we could
allow a mere rep:policy update. better to confirm with the oak team.
> Check for index definitions also considers ACL entries
> ------------------------------------------------------
>
> Key: JCRVLT-343
> URL: https://issues.apache.org/jira/browse/JCRVLT-343
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.4
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: package-maven-plugin-1.0.5
>
>
> The package for acs-aem-commons contains a rep:policy node at
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jcr_root/_oak_index/_rep_policy.xml.
> This leads to the exception {{Package should not contain index definitions,
> because 'allowIndexDefinitions=false'.}}
> Either the check should be relaxed to skip rep:policy nodes or the warning
> message should be adjusted.
> The issue was originally reported through
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1988.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
