Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)

Yes I understand that indeed M2E only understands javac.
But I have three questions then:
* Since neither javac nor jdt is executed by M2E when working in Eclipse, could not the compiler ID be ignored by M2E instead of shouting an error, or instead could it be simply a warning indicating that M2E has no idea on how to handle this? * I really don't like the idea that I have to modify my pom.xml to make M2E "work". I find this totally in the opposite spirit of IDE independence of Maven. Couldn't this be fixed in another manner (like a setting in Eclipse or a preference somewhere?) * Is there a way to simply remove all these Errors M2E reports (again a setting in Eclipse, a preference somewhere)?

Anyway, thanks for your quick reply,


Le 2/11/2011 11:15, Igor Fedorenko a écrit :
Out of the box, m2e only supports maven compiler plugin with
compilerId=javac. To make it work for other compilers, compilerId=jdt in
your specific case, you need to add this explicit lifecycle mapping
configuration in your (parent) pom.xml


Please see [1] for more information about lifecycle mapping
configuration and syntax.



On 11-11-02 10:30 AM, Guillaume Polet wrote:
Hi List,

I know I am not the first to ask this question, but I want to make sure
I understand correctly the error I am seeing in Eclipse with m2e 1.0.100
on all my Maven projects.

So I have a large multi-module Maven project and almost all of them show
me an error with the message "/Plugin execution not covered by lifecycle
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution:
phase: compile)/", and the same thing for testCompile.
I have recently modified the compiler used by m-c-p to use this one
(since the one from Oracle lamely crashes while compiling):

So, my understanding is that M2E puts an error on my pom.xml (and
therefore my project) because it does not handle directly this
configuration of the maven-compiler? Is this correct?
If yes, is not it a bit strong to put an error on this while we know
that the eclipse compiler will do the job anyway? I was quite frustrated
to see that now all my projects are marked as in error while they all work.

I can definitely not tell other developers that they first have to
select all 66 projects and go on them one by one to indicate that M2E
can safely ignore this. Could not this be simply a warning instead of an

Or am I just not understanding something on the way M2E and Eclipse work

Thanks in advance,


m2e-users mailing list
m2e-users mailing list

Back to the top