Decide M2E Life Cycle Configurations

Question

Importing a Maven project into Eclipse caused an error:

Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:gwt-maven-plugin:2.1.0:resources (execution: default, phase: process-resources) 

I'm not a Maven expert, but it seems like a problem when M2E needs explicit instructions on how to handle plugins related to certain events .

Eclipse offers a quick fix to just ignore these plugins, but you also have the option to run plugins or install / create a project configurator .

Given that most people (including me) are not going to create the M2E extension, what general rules should be used to determine whether to ignore or execute plugins? It seems to me that these plugins are included for some reason, so should they be executed by default? Or is there some reason why default execution is a bad idea?

Answer 1

The Eclipse build life cycle runs multiple times behind the scenes if the Create Automatically feature is enabled.

Thus, we do not want the Maven Eclipse plugin to perform heavy tasks that consume IO / CPU. For example, copying dependencies or creating package files.

It is better to run these commands manually from the command line.