Expand my Community achievements bar.

SOLVED

AEM Package & GitLab CI: [ERROR] Refuse to merge inline filters and non-sourced filter.xml

Avatar

Level 2

I'm trying to learn AEM and GitLab CI pipeline and can't seem to build on the first stage. Any advice on configuring the Filevault Package Manager plugin would be greatly appreciated. Thank you for your time.

 

Here is the error output:

[ERROR] Refuse to merge inline filters and non-sourced filter.xml. If this is intended, specify the filter.xml via the 'filterSource' property.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Superscript 0.0.1-SNAPSHOT:
[INFO] 
[INFO] Superscript ........................................ SUCCESS [  8.998 s]
[INFO] Superscript - Core ................................. SUCCESS [01:35 min]
[INFO] Superscript - UI Frontend .......................... SUCCESS [ 27.525 s]
[INFO] Superscript - Repository Structure Package ......... FAILURE [  0.555 s]
[INFO] Superscript - UI apps .............................. SKIPPED
[INFO] Superscript - UI content ........................... SKIPPED
[INFO] Superscript - UI config ............................ SKIPPED
[INFO] Superscript - All .................................. SKIPPED
[INFO] Superscript - Integration Tests .................... SKIPPED
[INFO] Superscript - Dispatcher ........................... SKIPPED
[INFO] Superscript - UI Tests ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:57 min
[INFO] Finished at: 2022-05-11T21:24:19Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.6:generate-metadata (default-generate-metadata) on project superscript.ui.apps.structure: Conflicting filters, look at above log for details. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.6:generate-metadata (default-generate-metadata) on project superscript.ui.apps.structure: Conflicting filters, look at above log for details.
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:306)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:211)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:165)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:157)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:121)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:127)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Conflicting filters, look at above log for details.
    at org.apache.jackrabbit.filevault.maven.packaging.GenerateMetadataMojo.computeFilters (GenerateMetadataMojo.java:558)
    at org.apache.jackrabbit.filevault.maven.packaging.GenerateMetadataMojo.execute (GenerateMetadataMojo.java:479)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:301)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:211)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:165)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:157)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:121)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:127)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

 

yml file:

Screen Shot 2022-05-11 at 12.44.55 PM.png

 

Filevault plugin config in main pom.xml:

Screen Shot 2022-05-11 at 12.45.57 PM.png

 

filter.xml in src/main/content/META-INF/vault/filter.xml:

Screen Shot 2022-05-11 at 12.48.57 PM.png

1 Accepted Solution

Avatar

Correct answer by
Level 2

I changed to "mvn clean package" and the CI job passed.

View solution in original post

2 Replies

Avatar

Community Advisor

Hi,

Can you try executing a command in debug mode to get more details on the issue?



Arun Patidar

Avatar

Correct answer by
Level 2

I changed to "mvn clean package" and the CI job passed.