[
https://issues.apache.org/jira/browse/JCRVLT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289896#comment-17289896
]
Konrad Windszus commented on JCRVLT-496:
----------------------------------------
[~dsuess] Currently in
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en#deploying-index-definitions
you can read:
bq. There is a known issue with Jackrabbit Filevault Maven Package Plugin
version 1.1.0 which does not allow you to add oak:index to modules of
<packageType>application</packageType>. To work around this, please use version
1.0.4.
Without this fix, customers need to either disable validation or use 1.0.4. So
either Adobe needs to fix the documentation to state that oak:indexes should
rather be part of a separate "content" type package or should have an interest
to get this fixed....
> 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)
