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)

The "jdt" id doesn't exist, you must use "eclipse". See 

On Sun, Jan 22, 2012 at 4:35 PM, Stephan Herrmann <stephan@xxxxxxxxxxxxxxx> wrote:
Thanks, Fred, much appreciated.

Just a quick question:
Previous examples I saw used to specify a compilerId of "jdt".
What's the difference when saying "eclipse" instead of "jdt"?


On Sunday, January 22, 2012 04:15:06 PM Fred Bricon wrote:
> Hi,
> FWIW, I've created a plugin to allow maven-compiler-plugin using
> compilerId=eclipse to be used transparently with m2e (by
> using org.eclipse.m2e.jdt.javaConfigurator).
> Source code is available from
> now (I may transfer it
> to the jbosstools organization later this week),
> but most importantly, you can install ci builds from this p2 update site :
> Using this eclipse plugin, no new lifecycle mapping is necessary in your
> pom.xml.
> Fred Bricon

m2e-users mailing list

"Have you tried turning it off and on again" - The IT Crowd

Back to the top