Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[m2e-users] Conflicting lifecycle mapping on maven-compiler-plugin

Hi all,

After upgrading to M2E 1.6 on Luna, I'm facing a weird problem.

M2E reports errors on my projects complaining about :

Conflicting lifecycle mapping (plugin execution "org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (execution: default-compile, phase: compile)"). To enable full functionality, remove the conflicting mapping and run Maven->Update Project Configuration.

and :
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (execution: default-compile, phase: compile)

Same for the testCompile goal.

The fact is that I've overridden the compile goal with the following definition in order to leverage the groovy-eclipse-compiler :

            <!-- set verbose to be true if you want lots of uninteresting messages -->
            <!-- <verbose>true</verbose> -->

Everything ran smoothly on M2E 1.5. Of course, the necessary configurators are installed to take care of the groovy-eclipse-compiler.

Thanks in advance for any help,


Back to the top