Unable to compile due to M2Eclipse which connector cannot find

Question

There is a section in the pom.xml file that requires Maven-Replacer-Plugin and (I believe) GitDescribe.

Here are the errors he gives me:

The execution of the plugin does not extend to the configuration of the life cycle: com.lukegb.mojo: gitdescribe-maven-plugin: 1.3: gitdescribe (execution: default, phase: compilation)

The execution of plugins does not extend to the configuration of the life cycle: com.google.code.maven-replacer-plugin: maven-replacer-plugin: 1.3.8: replace (execution: default, phase: generate resources)

Answer 1

This error has been well described in their documentation .

This feature was added in M2Eclipse 1.0 (now m2e). This caused a lot of trouble, as reported in this blog post .

One solution was to contaminate pom.xml with the plugin's lifecycle mapping metadata data, but that was not very satisfactory.

In m2e 1.1, plugin developers could embed a file called lifecycle-mapping-metadata.xml in their plugins to make it work in Eclipse (see M2E-compatible maven plugins ).

Fortunately, starting with m2e 1.2, everything has changed, and now we can configure it in the Eclipse settings (see the Eclipse lifecycle metadata metadata ).

Answer 2

This message appears because m2e does not know what to do at this point. The build should work with the maven command line, but m2e wants you to specify whether you want it to run the plugin or not.

The fix depends on what you want. You can either force eclipse to ignore the plugin, or execute it as part of the assembly.

The documentation explains this in more detail here, but I am copying the simple answer below. https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html

This modifies pom to add some eclipse metadata. If you are just trying to create it, this will work.

TIP. Use a quick fix to create an ignore mapping, then replace the action with. M2Eclipse 1.3 and newer is considered safer runOnIncremental = false by default. It is always recommended that the specific required runOnIncremental value be explicitly in the display configuration life cycle.

You can also change your settings in new versions of eclipse / m2e. This is another quick fix option. You can change this under "Project Properties" -> Maven-> Life Cycle Display.