blocks|key|239836|text|这是一段时间之前引入的M2E插件的一个“特性”。这与Maven插件没有直接关系，但也会发生在大多数其他JBoss插件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|239837|如果您在pom中定义了插件执行(如maven-ear-plugin:generate-application-xml的执行)，则还需要为M2E添加额外的配置信息，以告诉M2E在Eclipse中运行构建时要做什么，例如，插件执行是否应由M2E忽略或执行，是否也应对增量构建执行，...如果缺少该信息，M2E将通过显示以下错误消息对其进行警告：|offset|length|style|CODE|239838|239839|“插件执行不在生命周期配置范围内”|blockquote|239840|239841|239842|有关更详细的解释和一些示例配置，请参阅此处，这些配置需要添加到pom中，以消除该错误：|239843|https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html|239844|entityMap|0|LINK|mutability|MUTABLE|url^0|0|4|3|H|15|0|0|0|0|0|0|0|20|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|R|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Q]]]]

This is a "feature" of the M2E plugin that had been introduced a while ago. It's not directly related to the JBoss EAR plugin but also happens with most other Maven plugins.

If you have a plugin execution defined in your <code>pom</code> (like the execution of <code>maven-ear-plugin:generate-application-xml</code>), you also need to add additional config information for M2E that tells M2E what to do when the build is run in Eclipse, e.g. should the plugin execution be ignored or executed by M2E, should it be also done for incremental builds, ... If that information is missing, M2E complains about it by showing this error message:

<blockquote>
 "Plugin execution not covered by lifecycle configuration"
</blockquote>

See here for a more detailed explanation and some sample config that needs to be added to the pom to make that error go away:

<a href="https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html" rel="nofollow noreferrer">https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html</a>

blocks|key|240931|text|我尝试在清理后立即执行特定的插拔，即清理后(默认是清理阶段)。对于eclipse+indigo，这对我很有效。只是添加了post-clean为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240932|<executions>
++<execution>
++++<configuration>
++++</configuration>
+++<phase>post-clean</phase>
++++<goals>
++++++<goal>update-widgetset</goal>
++++</goals>
++</execution>
</executions>+|code-block|syntax|javascript|240933|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I tried to execute specific plugging right after clean up i.e. post-clean (default is clean phase). This worked for me with eclipse indigo. Just added post-clean resolved the problem for me. 

<pre><code>&lt;executions&gt;
 &lt;execution&gt;
 &lt;configuration&gt;
 &lt;/configuration&gt;
 &lt;phase&gt;post-clean&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;update-widgetset&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
&lt;/executions&gt; 
</code></pre>

blocks|key|240938|text|使用Jan回答中解释的机制，我已经指示应用程序插件忽略“generate-+m2e+-xml”的目标。因为m2e创建了application.xml，所以这样做消除了错误，并且似乎起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240939|因此，基本上这个错误迫使我们决定，当Maven构建在m2e插件的控制下在Eclipse中运行时，负责生成application.xml的是哪种机制。我们已经决定让m2e来负责。|240940|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-ear-plugin</artifactId>
++++++++++++<version>2.6</version>
++++++++++++<configuration>
++++++++++++++++<version>6</version>
++++++++++++++++<defaultLibBundleDir>lib</defaultLibBundleDir>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
++++<pluginManagement>
++++++++<plugins>
++++++++++++**
++++++++++++<plugin>
++++++++++++++++<groupId>org.eclipse.m2e</groupId>
++++++++++++++++<artifactId>lifecycle-mapping</artifactId>
++++++++++++++++<version>1.0.0</version>
++++++++++++++++<configuration>
++++++++++++++++++++<lifecycleMappingMetadata>
++++++++++++++++++++++++<pluginExecutions>
++++++++++++++++++++++++++++<pluginExecution>
++++++++++++++++++++++++++++++++<pluginExecutionFilter>
++++++++++++++++++++++++++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++++++++++++++++++++++++++<artifactId>maven-ear-plugin</artifactId>
++++++++++++++++++++++++++++++++++++<versionRange>[2.1,)</versionRange>
++++++++++++++++++++++++++++++++++++<goals>
++++++++++++++++++++++++++++++++++++++++<goal>generate-application-xml</goal>
++++++++++++++++++++++++++++++++++++</goals>
++++++++++++++++++++++++++++++++</pluginExecutionFilter>
++++++++++++++++++++++++++++++++<action>
++++++++++++++++++++++++++++++++++++<ignore></ignore>
++++++++++++++++++++++++++++++++</action>
++++++++++++++++++++++++++++</pluginExecution>
++++++++++++++++++++++++</pluginExecutions>
++++++++++++++++++++</lifecycleMappingMetadata>
++++++++++++++++</configuration>
++++++++++++</plugin>**
++++++++</plugins>
++++</pluginManagement>
</build>|code-block|syntax|javascript|240941|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

With the mechanism explained in the answer of Jan I have instructed the m2e pluging to ignore the goal "generate-application-xml". This gets rid of the error and seems to work since m2e creates application.xml.

So basically the error forced us to decide which mechanism is in charge for generating application.xml when the Maven build runs inside Eclipse under the control of the m2e plugin. And we have decided that m2e is in charge.

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-ear-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.6&lt;/version&gt;
 &lt;configuration&gt;
 &lt;version&gt;6&lt;/version&gt;
 &lt;defaultLibBundleDir&gt;lib&lt;/defaultLibBundleDir&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;pluginManagement&gt;
 &lt;plugins&gt;
 **&lt;!-- This plugin's configuration is used to store Eclipse m2e settings 
 only. It has no influence on the Maven build itself. --&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt;
 &lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt;
 &lt;version&gt;1.0.0&lt;/version&gt;
 &lt;configuration&gt;
 &lt;lifecycleMappingMetadata&gt;
 &lt;pluginExecutions&gt;
 &lt;pluginExecution&gt;
 &lt;pluginExecutionFilter&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-ear-plugin&lt;/artifactId&gt;
 &lt;versionRange&gt;[2.1,)&lt;/versionRange&gt;
 &lt;goals&gt;
 &lt;goal&gt;generate-application-xml&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/pluginExecutionFilter&gt;
 &lt;action&gt;
 &lt;ignore&gt;&lt;/ignore&gt;
 &lt;/action&gt;
 &lt;/pluginExecution&gt;
 &lt;/pluginExecutions&gt;
 &lt;/lifecycleMappingMetadata&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;**
 &lt;/plugins&gt;
 &lt;/pluginManagement&gt;
&lt;/build&gt;
</code></pre>

blocks|key|242583|text|无论如何，为时已晚，但我的解决方案很简单，就是右键单击Eclipse中的错误消息，然后为每个出现此类错误的pom选择Quick+Fix+>>+Ignore|type|unstyled|depth|inlineStyleRanges|entityRanges|data|242584|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

anyway it's too late but my solution was simple right-click on error-message in Eclipse and choosing Quick Fix >> Ignore for every pom with such errors

blocks|key|3123152|text|您需要理解M2E_plugin_execution_not_covered中的内容，并遵循下面提到的步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3123153|3123154|从eclipse插件文件夹中选择org.eclipse.m2e.lifecyclemapping.defaults+jar，将其解压缩，然后打开|unordered-list-item|3123155|-|3123156|-org.eclipse.m2e.lifecyclemapping.defaults-metadata.xml，您可以在其中找到插件的所有错误，这些错误在<action>标记下显示为带有错误的pluginExecutions。|style|CODE|3123157|3123158|例如:对于write-project-properties错误，在lifecycle-mapping-metadata.xml文件的<pluginExecutions>部分下添加以下代码片段：|3123159|+<pluginExecution>
++++<pluginExecutionFilter>
+++++++<groupId>org.codehaus.mojo</groupId>
+++++++<artifactId>properties-maven-plugin</artifactId>
+++++++<versionRange>1.0-alpha-2</versionRange>
+++++++<goals>
+++++++++<goal>write-project-properties</goal>
+++++++</goals>
++++</pluginExecutionFilter>
+++++<action>
+++++++<ignore+/>
+++++</action>
+++</pluginExecution>|code-block|syntax|javascript|3123160|Eclipse|3123161|替换了JAR中XML文件，|3123162|
|3123163|替换了Eclipse的plugin+folder|3123164|3123165|Restart+|3123166|3123167|3123168|
中更新的JAR|3123169|您应该不会在将来看到任何项目的错误。|3123170|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.eclipse.org/M2E_plugin_execution_not_covered#ignore_plugin_goal^0|5|W|0|0|0|0|0|25|8|0|0|1U|I|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|D|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1P|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|1R|8|@$A|1S|B|1T|L|M]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1V|8|@$A|1W|B|1X|L|M]]|9|@]|C|$]]|$1|Q|3|R|5|S|7|1Y|8|@]|9|@]|C|$T|U]]|$1|V|3|W|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|X|3|Y|5|G|7|20|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|21|8|@]|9|@]|C|$]]|$1|11|3|12|5|G|7|22|8|@]|9|@]|C|$]]|$1|13|3|10|5|6|7|23|8|@]|9|@]|C|$]]|$1|14|3|15|5|G|7|24|8|@]|9|@]|C|$]]|$1|16|3|10|5|6|7|25|8|@]|9|@]|C|$]]|$1|17|3|-4|5|G|7|26|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|27|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|6|7|28|8|@]|9|@]|C|$]]|$1|1C|3|-4|5|6|7|29|8|@]|9|@]|C|$]]]|1D|$1E|$5|1F|1G|1H|C|$1I|1J]]]]

You need to understand the content in <a href="http://wiki.eclipse.org/M2E_plugin_execution_not_covered#ignore_plugin_goal" rel="nofollow">M2E_plugin_execution_not_covered</a> and follow the steps mentioned below:

<ul>
<li>Pick org.eclipse.m2e.lifecyclemapping.defaults jar from the eclipse plugin folder</li>
<li>Extract it and open lifecycle-mapping-metadata.xml where you can find all the pluginExecutions.</li>
<li>Add the pluginExecutions of your plugins which are shown as errors with <code>&lt;ignore/&gt;</code> under <code>&lt;action&gt;</code> tags.</li>
</ul>

eg: for write-project-properties error, add this snippet under the <code>&lt;pluginExecutions&gt;</code> section of the lifecycle-mapping-metadata.xml file:

<pre><code> &lt;pluginExecution&gt;
 &lt;pluginExecutionFilter&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-maven-plugin&lt;/artifactId&gt;
 &lt;versionRange&gt;1.0-alpha-2&lt;/versionRange&gt;
 &lt;goals&gt;
 &lt;goal&gt;write-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/pluginExecutionFilter&gt;
 &lt;action&gt;
 &lt;ignore /&gt;
 &lt;/action&gt;
 &lt;/pluginExecution&gt;
</code></pre>

<ul>
<li>Replace that XML file in the JAR</li>
<li>Replace the updated JAR in Eclipse's plugin folder</li>
<li>Restart Eclipse</li>
</ul>

You should see no errors in the future for any project.

blocks|key|242622|text|从Maven+Eclipse+(+m2e+)版本0.12开始，所有的m2e生命周期目标都必须映射到已安装的Maven扩展。在本例中，maven-ear-plugin有一个未映射的目标default-generate-application-xml。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|242623|您只需遵循此处的说明即可排除未映射的生命周期目标：|242624|https://wiki.eclipse.org/M2E_plugin_execution_not_covered|242625|或者，只需在Eclipse中右键单击错误消息并选择Quick+Fix+->+Ignore+for+every+pom+with+such+errors。|242626|在忽略生命周期目标时应该小心:通常情况下，目标会做一些有用的事情，如果在Eclipse中将其配置为忽略，则可能会错过重要的构建步骤。您可能还想考虑添加对Maven+Eclipse+EAR扩展的支持，以实现未映射的生命周期目标。|242627|entityMap|0|LINK|mutability|MUTABLE|url|https://www.eclipse.org/m2e/|1^0|1U|G|2J|W|1|D|0|0|0|0|1L|1|0|P|9|12|11|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|J|3|K|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1E|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|I]]]]

As of <a href="https://www.eclipse.org/m2e/" rel="nofollow">Maven Eclipse</a> (m2e) version 0.12 all Maven life-cycle goals must map to an installed m2e extension. In this case, the <code>maven-ear-plugin</code> had an-unmapped goal <code>default-generate-application-xml</code>.

You can exclude un-mapped life-cycle goals by simply following the instructions here:

<a href="https://wiki.eclipse.org/M2E_plugin_execution_not_covered" rel="nofollow">https://wiki.eclipse.org/M2E_plugin_execution_not_covered</a>

Alternatively, simply right-click on the error message in Eclipse and choosing <code>Quick Fix</code> -> <code>Ignore for every pom with such errors</code>.

You should be careful when ignoring life-cycle goals: typically goals do something useful and if you configure them to be ignored in Eclipse you may miss important build steps. You might also want to consider adding support to the Maven Eclipse EAR extension for the unmapped life-cycle goal.

blocks|key|2908824|text|Eclipse已经了解了增量builds.This的概念，它非常有用，因为它节省了大量时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2908825|这个有什么用？|offset|length|style|BOLD|2908826|假设您刚刚更改了单个.java文件。增量构建器将能够编译代码，而不必重新编译所有内容(这将需要更多时间)。|2908827|Maven+Plugins有什么问题吗|2908828|大多数maven插件都不是为增量构建而设计的，因此它给m2e带来了麻烦。m2e不知道插件的目标是关键的还是无关紧要的。如果它只是在单个文件发生变化时执行每个插件，这将花费大量时间。|2908829|这就是为什么m2e依赖于元数据信息来确定应该如何处理执行。m2e已经提出了不同的选项来提供此元数据信息，并且首选顺序如下(从高到低)|2908830|project|2908831|parent，祖父母的|unordered-list-item|2908832|pom.xml文件等pom.xml文件|ordered-list-item|2908833|+m2e+1.2%2B工作区maven+m2e+1.1%2B生命周期映射元数据随m2e|2908834|提供的生命周期映射元数据|2908835|2908836|1,2是指在pom文件或其父文件的标签中指定pluginManagement部分。M2E读取此配置以配置project.Below代码片段，指示m2e忽略yuicompressor+maven-plugin的jslint和compress目标|CODE|2908837|<pluginManagement>
++++++++<plugins>
++++++++++++
++++++++++++<plugin>
++++++++++++++++<groupId>org.eclipse.m2e</groupId>
++++++++++++++++<artifactId>lifecycle-mapping</artifactId>
++++++++++++++++<version>1.0.0</version>
++++++++++++++++<configuration>
++++++++++++++++++++<lifecycleMappingMetadata>
++++++++++++++++++++++++<pluginExecutions>
++++++++++++++++++++++++++++<pluginExecution>
++++++++++++++++++++++++++++++++<pluginExecutionFilter>
++++++++++++++++++++++++++++++++++++<groupId>net.alchim31.maven</groupId>
++++++++++++++++++++++++++++++++++++<artifactId>yuicompressor-maven-plugin</artifactId>
++++++++++++++++++++++++++++++++++++<versionRange>[1.0,)</versionRange>
++++++++++++++++++++++++++++++++++++<goals>
++++++++++++++++++++++++++++++++++++++++<goal>compress</goal>
++++++++++++++++++++++++++++++++++++++++<goal>jslint</goal>
++++++++++++++++++++++++++++++++++++</goals>
++++++++++++++++++++++++++++++++</pluginExecutionFilter>
++++++++++++++++++++++++++++++++<action>
++++++++++++++++++++++++++++++++++++<ignore+/>
++++++++++++++++++++++++++++++++</action>
++++++++++++++++++++++++++++</pluginExecution>
++++++++++++++++++++++++</pluginExecutions>
++++++++++++++++++++</lifecycleMappingMetadata>
++++++++++++++++</configuration>
++++++++++++</plugin>
++++++++</plugins>
++++</pluginManagement>|code-block|syntax|javascript|2908838|3)如果你不想用这些元数据污染你的pom文件，你可以把它存储在一个外部的XML文件中(选项3)。下面是一个示例映射文件，它指示m2e忽略yuicompressor-maven-plugin的jslint和compress目标|2908839|<?xml+version="1.0"+encoding="UTF-8"?>
<lifecycleMappingMetadata>
++++<pluginExecutions>
++++++++<pluginExecution>
++++++++++++<pluginExecutionFilter>
++++++++++++++++<groupId>net.alchim31.maven</groupId>
++++++++++++++++<artifactId>yuicompressor-maven-plugin</artifactId>
++++++++++++++++<versionRange>[1.0,)</versionRange>
++++++++++++++++<goals>
++++++++++++++++++++<goal>compress</goal>
++++++++++++++++++++<goal>jslint</goal>
++++++++++++++++</goals>
++++++++++++</pluginExecutionFilter>
++++++++++++<action>
++++++++++++++++<ignore/>
++++++++++++</action>
++++++++</pluginExecution>
++++</pluginExecutions>
</lifecycleMappingMetadata>|2908840|4)如果您不喜欢这3个选项中的任何一个，您可以使用m2e连接器(扩展)，因为maven+plugin.The连接器将反过来向m2e提供元数据。您可以在此link中看到连接器中的元数据信息示例。您可能已经注意到，元数据引用了一个配置器。这仅仅意味着m2e将把责任委派给由扩展author.The配置器提供的特定java类，该类可以配置项目(例如，添加额外的源文件夹等)，并决定是否在增量构建期间执行实际的maven插件(如果在配置器中没有得到适当的管理，可能会导致无休止的项目构建)。|2908841|有关配置器(link1、link2)的示例，请参阅这些链接。因此，如果插件是可以通过外部连接器管理的，那么您可以安装它。m2e维护由其他developers.This提供的此类连接器的列表，称为发现目录。如果您还没有通过任何选项(1-6)执行的生命周期映射元数据，并且发现目录有一些可以管理执行的扩展，那么m2e将提示您安装连接器。|2908842|下图显示了m2e如何提示您安装build-helper-maven-plugin的连接器。|2908843|📷|atomic|2908844|。|2908845|5)m2e鼓励插件作者支持增量构建，并在maven-plugin中提供生命周期映射itself.This将意味着用户不必使用任何额外的生命周期映射，或者connectors.Some插件作者拥有already+implemented+this|2908846|6)默认情况下，m2e保存了大多数常用插件的生命周期映射元数据，比如maven编译器插件和许多其他插件。|2908847|现在回到问题:您可能只需要在1、2或3中为给您带来麻烦的特定目标提供一个忽略生命周期映射。|2908848|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/lifecycle-mapping-metadata.xml|1|https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/src/com/coderplus/m2e/remoteresourcescore/CoderPlusProjectConfigurator.java|2|https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/src/com/coderplus/m2e/remoteresourcescore/CoderPlusBuildParticipant.java|3|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b35705232984c281a2a3b806cb1cf65e.png|imageAlt|4|https://github.com/highsource/maven-jaxb2-plugin/blob/master/plugin-2.2/src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml^0|0|0|2|0|0|0|0|0|0|0|0|0|0|0|2W|6|33|8|0|0|2N|6|2U|8|0|0|24|4|0|0|6|5|1|C|5|2|0|0|0|1|3|0|0|2P|O|4|0|0|0^^$0|@$1|2|3|4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2G|8|@$D|2H|E|2I|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|2J|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|2K|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2L|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|2M|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2N|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|2O|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|2P|8|@]|9|@]|A|$]]|$1|X|3|Y|5|W|7|2Q|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2R|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2T|8|@$D|2U|E|2V|F|14]|$D|2W|E|2X|F|14]]|9|@]|A|$]]|$1|15|3|16|5|17|7|2Y|8|@]|9|@]|A|$18|19]]|$1|1A|3|1B|5|6|7|2Z|8|@$D|30|E|31|F|14]|$D|32|E|33|F|14]]|9|@]|A|$]]|$1|1C|3|1D|5|17|7|34|8|@]|9|@]|A|$18|19]]|$1|1E|3|1F|5|6|7|35|8|@]|9|@$D|36|E|37|1|38]]|A|$]]|$1|1G|3|1H|5|6|7|39|8|@]|9|@$D|3A|E|3B|1|3C]|$D|3D|E|3E|1|3F]]|A|$]]|$1|1I|3|1J|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|1M|7|3H|8|@]|9|@$D|3I|E|3J|1|3K]]|A|$]]|$1|1N|3|1O|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|3M|8|@]|9|@$D|3N|E|3O|1|3P]]|A|$]]|$1|1R|3|1S|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]]|1W|$1X|$5|1Y|1Z|20|A|$21|22]]|23|$5|1Y|1Z|20|A|$21|24]]|25|$5|1Y|1Z|20|A|$21|26]]|27|$5|28|1Z|29|A|$2A|2B|2C|-4]]|2D|$5|1Y|1Z|20|A|$21|2E]]]]

Eclipse has got the concept of incremental builds.This is incredibly useful as it saves a lot of time. 

How is this Useful

Say you just changed a single .java file. The incremental builders will be able to compile the code without having to recompile everything(which will take more time).

Now what's the problem with Maven Plugins

Most of the maven plugins aren't designed for incremental builds and hence it creates trouble for m2e. m2e doesn't know if the plugin goal is something which is crucial or if it is irrelevant. If it just executes every plugin when a single file changes, it's gonna take lots of time. 

This is the reason why m2e relies on metadata information to figure out how the execution should be handled. m2e has come up with different options to provide this metadata information and the order of preference is as below(highest to lowest)

<ol>
<li>pom.xml file of the project</li>
<li>parent, grand-parent and so on pom.xml files</li>
<li>[m2e 1.2+] workspace preferences</li>
<li>installed m2e extensions</li>
<li>[m2e 1.1+] lifecycle mapping metadata provided by maven plugin</li>
<li>default lifecycle mapping metadata shipped with m2e</li>
</ol>

1,2 refers to specifying pluginManagement section in the tag of your pom file or any of it's parents. M2E reads this configuration to configure the project.Below snippet instructs m2e to ignore the <code>jslint</code> and <code>compress</code> goals of the yuicompressor-maven-plugin

<pre><code>&lt;pluginManagement&gt;
 &lt;plugins&gt;
 &lt;!--This plugin's configuration is used to store Eclipse m2e settings 
 only. It has no influence on the Maven build itself. --&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt;
 &lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt;
 &lt;version&gt;1.0.0&lt;/version&gt;
 &lt;configuration&gt;
 &lt;lifecycleMappingMetadata&gt;
 &lt;pluginExecutions&gt;
 &lt;pluginExecution&gt;
 &lt;pluginExecutionFilter&gt;
 &lt;groupId&gt;net.alchim31.maven&lt;/groupId&gt;
 &lt;artifactId&gt;yuicompressor-maven-plugin&lt;/artifactId&gt;
 &lt;versionRange&gt;[1.0,)&lt;/versionRange&gt;
 &lt;goals&gt;
 &lt;goal&gt;compress&lt;/goal&gt;
 &lt;goal&gt;jslint&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/pluginExecutionFilter&gt;
 &lt;action&gt;
 &lt;ignore /&gt;
 &lt;/action&gt;
 &lt;/pluginExecution&gt;
 &lt;/pluginExecutions&gt;
 &lt;/lifecycleMappingMetadata&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/pluginManagement&gt;
</code></pre>

3) In case you don't prefer polluting your pom file with this metadata, you can store this in an external XML file(option 3). Below is a sample mapping file which instructs m2e to ignore the <code>jslint</code> and <code>compress</code> goals of the yuicompressor-maven-plugin

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;lifecycleMappingMetadata&gt;
 &lt;pluginExecutions&gt;
 &lt;pluginExecution&gt;
 &lt;pluginExecutionFilter&gt;
 &lt;groupId&gt;net.alchim31.maven&lt;/groupId&gt;
 &lt;artifactId&gt;yuicompressor-maven-plugin&lt;/artifactId&gt;
 &lt;versionRange&gt;[1.0,)&lt;/versionRange&gt;
 &lt;goals&gt;
 &lt;goal&gt;compress&lt;/goal&gt;
 &lt;goal&gt;jslint&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/pluginExecutionFilter&gt;
 &lt;action&gt;
 &lt;ignore/&gt;
 &lt;/action&gt;
 &lt;/pluginExecution&gt;
 &lt;/pluginExecutions&gt;
&lt;/lifecycleMappingMetadata&gt;
</code></pre>

4) In case you don't like any of these 3 options, you can use an m2e connector(extension) for the maven plugin.The connector will in turn provide the metadata to m2e. You can see an example of the metadata information within a connector at this <a href="https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/lifecycle-mapping-metadata.xml" rel="noreferrer">link</a> . You might have noticed that the metadata refers to a configurator. This simply means that m2e will delegate the responsibility to that particular java class supplied by the extension author.The configurator can configure the project(like say add additional source folders etc) and decide whether to execute the actual maven plugin during an incremental build(if not properly managed within the configurator, it can lead to endless project builds)

Refer these links for an example of the configuratior(<a href="https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/src/com/coderplus/m2e/remoteresourcescore/CoderPlusProjectConfigurator.java" rel="noreferrer">link1</a>,<a href="https://github.com/coderplus/m2e-connector-for-maven-remote-resources-plugin/blob/master/core/src/com/coderplus/m2e/remoteresourcescore/CoderPlusBuildParticipant.java" rel="noreferrer">link2</a>). So in case the plugin is something which can be managed via an external connector then you can install it. m2e maintains a list of such connectors contributed by other developers.This is known as the discovery catalog. m2e will prompt you to install a connector if you don't already have any lifecycle mapping metadata for the execution through any of the options(1-6) and the discovery catalog has got some extension which can manage the execution.

The below image shows how m2e prompts you to install the connector for the build-helper-maven-plugin.
<img src="https://i.stack.imgur.com/ZbWEa.png" alt="install connector suggested from the discovery catalog">. 

5)m2e encourages the plugin authors to support incremental build and supply lifecycle mapping within the maven-plugin itself.This would mean that users won't have to use any additional lifecycle mappings or connectors.Some plugin authors have <a href="https://github.com/highsource/maven-jaxb2-plugin/blob/master/plugin-2.2/src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml" rel="noreferrer">already implemented this</a>

6) By default m2e holds the lifecycle mapping metadata for most of the commonly used plugins like the maven-compiler-plugin and many others.

Now back to the question :You can probably just provide an ignore life cycle mapping in 1, 2 or 3 for that specific goal which is creating trouble for you.

blocks|key|237567|text|提醒您m2e可以更好地配置，而不是项目继承假阳性错误标记的一个好办法是将这些错误降级为警告：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|237568|Window+->首选项->+Maven+->错误/警告->插件执行未涵盖生命周期配置=+Warning|237569|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A good workaround to remind you that m2e could be better configured, without the project inheriting a false positive error marker, is to just downgrade those errors to warnings:

Window -> Preferences -> Maven -> Errors/Warnings -> Plugin execution not covered by lifecycle configuration = Warning

blocks|key|3123416|text|尽管这个问题太老了，但我想分享对我有效的解决方案，因为当遇到这个错误时，我已经检查了所有东西。这是一种痛苦，我花了两天时间尝试，最后的解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3123417|更新eclipse中的M2e插件|offset|length|style|BOLD|3123418|清理并重新构建|3123419|entityMap^0|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Even though the question is too old, but I would like to share the solution that worked for me because I already checked everything when it comes to this error. It was a pain, I spent two days trying and at the end the solution was:

update the M2e plugin in eclipse 

clean and build again

I am using Eclipse 3.7 Indigo with Maven M2E Plugin 1.0.100.

Using the JBoss 7.x JavaEE 6 EAR archetype, the pom for EAR is giving me this error:

<blockquote>
 Plugin execution not covered by lifecycle configuration:
 org.apache.maven.plugins:maven-ear-plugin:2.6:generate-application-xml
 (execution: default-generate-application-xml, phase:
 generate-resources)
</blockquote>

<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-ear-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.6&lt;/version&gt;
 &lt;configuration&gt;
 &lt;!-- Tell Maven we are using Java EE 6 --&gt;
 &lt;version&gt;6&lt;/version&gt;
 &lt;!-- Use Java EE ear libraries as needed. Java EE ear libraries 
 are in easy way to package any libraries needed in the ear, and automatically 
 have any modules (EJB-JARs and WARs) use them --&gt;
 &lt;defaultLibBundleDir&gt;lib&lt;/defaultLibBundleDir&gt;
 &lt;modules&gt;&lt;/modules&gt;
 &lt;/configuration&gt;
&lt;plugin&gt;
</code></pre>

Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

编译器

Eclipse

Java

我正在使用Eclipse3.7 Indigo和Maven M2E插件1.0.100。使用JBoss 7.x JavaEE 6 EAR原型，EAR的pom给出了这个错误：未包含在生命周期配置中的应用程序插件执行: org.apache.maven.plugins:maven-ear-plugin:2.6:generate...

问插件执行不在生命周期配置范围内(JBossas 7 EAR原型)
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问插件执行不在生命周期配置范围内(JBossas 7 EAR原型)EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问插件执行不在生命周期配置范围内(JBossas 7 EAR原型)
EN