[
https://issues.apache.org/jira/browse/JCRVLT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290024#comment-17290024
]
Thomas Mueller commented on JCRVLT-496:
---------------------------------------
> Should index definitions be allowed by default or just if an explicit boolean
> flag is set inside application packages?
Whatever we need to do, we need to verify and possibly update the documentation
everywhere. Not just in the vault-doc.
Right now PackageTypeValidator.java has hardcoded paths for /apps + /libs,
which isn't nice. Having DEFAULT_IMMUTABLE_ROOT_NODE_NAMES is better, if there
is no way to auto-detect (?)
But the patch itself doesn't seem to introduce a flag? Maybe I didn't see it
yet... but "prohibitMutableContent" is already there it seems.
> Clarify usage of oak:index in application packages
> --------------------------------------------------
>
> Key: JCRVLT-496
> URL: https://issues.apache.org/jira/browse/JCRVLT-496
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.8
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.4.10
>
>
> Although according to JCRVLT-170 application packages must not contain oak
> index definitions, this is necessary though for AEM as a Cloud Service
> (https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en#index-management-using-blue-green-deployments
> and
> https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#mutable-vs-immutable).
> To allow validation of such application packages there should be a flag
> considered, which allows for oak index definitions inside application
> packages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
