Hi Daniel,
for Maven Plugins you can override dependencies locally like this:
<plugin>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>filevault-package-maven-plugin</artifactId>
<version>1.1.6</version>
<dependencies>
<dependency>
<groupId>org.apache.jackrabbit.vault</groupId>
<artifactId>org.apache.jackrabbit.vault</artifactId>
<version>3.4.10</version>
</dependency>
</dependencies>
Unfortunately JCRVLT-496 is not sufficient, but probably also
https://issues.apache.org/jira/browse/JCRVLT-513 is needed which is only fixed
in the upcoming FileVault version.
I plan to do a release next week.
I plan to do a new release of the filevault-package-maven-plugin also, but no
ETA for that yet...
Konrad
> On 19. May 2021, at 17:25, Daniel Iancu <[email protected]> wrote:
>
> Hi,
> Is it possible to have a new release for filevault-package-maven-plugin that
> includes filevault version 3.4.10 with the fix for
> https://issues.apache.org/jira/browse/JCRVLT-496 ? Latest version, 1.1.6 uses
> filevault-3.4.8.
>
> When we try to deploy an custom index for AEM following the instructions here
> [1] we get validation errors.
>
> ERROR] ValidationViolation: "jackrabbit-packagetype: Package of type
> 'APPLICATION' is not supposed to contain content outside '/libs' and
> '/apps'!", filePath=jcr_root/_oak_index/damAssetLucene-7-custom-2/tika,
> nodePath=/oak:index/damAssetLucene-7-custom-2/tika
>
> This can happen with any AEM project that is generated from the
> aem-project-archetype and adds a custom index.
>
> Thanks,
> Daniel
>
> [1]
> https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en#deploying-index-definitions
