Plugin execution not covered by lifecycle configuration JBossas 7 EAR archetype

Question

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      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     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

User · Answer

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

User · Answer

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    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

User · Answer

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

User · Answer

I was able to resolve the same problem with maven-antrun-plugin and jaxb2-maven-plugin in Eclipse Kepler 4 3 by appying this solution  http   wiki eclipse org M2E plugin execution not covered Eclipse 4 2 add default mapping  So the content of my  elipse workspace name   metadata  plugins org eclipse m2e core lifecycle-mapping-metadata xml is as follows    lt  xml version  1 0  encoding  UTF-8   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-antrun-plugin lt  artifactId gt           lt versionRange gt 1 3 lt  versionRange gt           lt goals gt             lt goal gt run lt  goal gt           lt  goals gt         lt  pluginExecutionFilter gt         lt action gt           lt ignore   gt         lt  action gt       lt  pluginExecution gt       lt pluginExecution gt         lt pluginExecutionFilter gt           lt groupId gt org codehaus mojo lt  groupId gt           lt artifactId gt jaxb2-maven-plugin lt  artifactId gt           lt versionRange gt 1 2 lt  versionRange gt           lt goals gt             lt goal gt xjc 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     Had to restart Eclipse to see the errors gone

User · Answer

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 pom  like the execution of maven-ear-plugin generate-application-xml   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       Plugin execution not covered by lifecycle configuration    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   https   www eclipse org m2e documentation m2e-execution-not-covered html

User · Answer

As of Maven Eclipse  m2e  version 0 12 all Maven life-cycle goals must map to an installed m2e extension  In this case  the maven-ear-plugin had an-unmapped goal default-generate-application-xml   You can exclude un-mapped life-cycle goals by simply following the instructions here   https   wiki eclipse org M2E plugin execution not covered  Alternatively  simply right-click on the error message in Eclipse and choosing Quick Fix -  Ignore for every pom with such errors   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

User · Answer

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     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

User · Answer

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

User · Answer

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    pom xml file of the project parent  grand-parent and so on pom xml files  m2e 1 2   workspace preferences installed m2e extensions  m2e 1 1   lifecycle mapping metadata provided by maven plugin default lifecycle mapping metadata shipped with m2e   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 jslint and compress goals of the yuicompressor-maven-plugin   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    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 jslint and compress goals of the yuicompressor-maven-plugin   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    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 link   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 link1 link2   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      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 already implemented this  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

User · Answer

You need to understand the content in  M2E plugin execution not covered and follow the steps mentioned below    Pick org eclipse m2e lifecyclemapping defaults jar from the eclipse plugin folder Extract it and open lifecycle-mapping-metadata xml where you can find all the pluginExecutions  Add the pluginExecutions of your plugins which are shown as errors with  lt ignore  gt  under  lt action gt  tags    eg  for write-project-properties error  add this snippet under the  lt pluginExecutions gt  section of the lifecycle-mapping-metadata xml file     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     Replace that XML file in the JAR Replace the updated JAR in Eclipse s plugin folder Restart Eclipse   You should see no errors in the future for any project

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

Examples related to maven

Examples related to jboss7.x

Examples related to m2eclipse

Examples related to maven-ear-plugin