How to solve Plugin execution not covered by lifecycle configuration for Spring Data Maven Builds

Question

I am trying to work with Spring Data and Neo4j  I started by trying to follow this guide linked to by the main site  In particular I based my pom xml off of the  Hello  World   example file  Here is a snip from my pom xml for the plugin that is causing the issues      lt plugin gt   lt  -- Required to resolve aspectj-enhanced class features -- gt       lt groupId gt org codehaus mojo lt  groupId gt       lt artifactId gt aspectj-maven-plugin lt  artifactId gt       lt version gt 1 0 lt  version gt       lt configuration gt           lt outxml gt true lt  outxml gt           lt aspectLibraries gt               lt aspectLibrary gt                   lt groupId gt org springframework lt  groupId gt                   lt artifactId gt spring-aspects lt  artifactId gt               lt  aspectLibrary gt               lt aspectLibrary gt                   lt groupId gt org springframework data lt  groupId gt                   lt artifactId gt spring-data-neo4j lt  artifactId gt               lt  aspectLibrary gt           lt  aspectLibraries gt           lt source gt 1 6 lt  source gt           lt target gt 1 6 lt  target gt       lt  configuration gt       lt executions gt           lt  -- ERROR HERE IN ECLIPSE SEE BELOW FOR FULL MESSAGE -- gt           lt execution gt               lt goals gt                   lt goal gt compile lt  goal gt                   lt goal gt test-compile lt  goal gt               lt  goals gt           lt  execution gt       lt  executions gt       lt dependencies gt           lt dependency gt               lt groupId gt org aspectj lt  groupId gt               lt artifactId gt aspectjrt lt  artifactId gt               lt version gt   aspectj version  lt  version gt           lt  dependency gt           lt dependency gt               lt groupId gt org aspectj lt  groupId gt               lt artifactId gt aspectjtools lt  artifactId gt               lt version gt   aspectj version  lt  version gt           lt  dependency gt       lt  dependencies gt   lt  plugin gt    The error I am seeing is    Multiple annotations found at this line      - Plugin execution not covered by lifecycle configuration  org codehaus mojo aspectj-maven-plugin 1 0 compile  execution  default  phase  process-classes      - Plugin execution not covered by lifecycle configuration  org codehaus mojo aspectj-maven-plugin 1 0 test-compile  execution  default  phase  process-classes    I am running Eclipse 3 6 2 and m2e 0 13  I m not a Maven expert  so please be very explanatory in your answers if possible   I ve also tried m2e 1 0 0 via this update site and still get the same error

User · Answer

See https   www eclipse org m2e documentation m2e-execution-not-covered html       To solve some long-standing issues    m2e 1 0 requires explicit instructions   what to do with all Maven plugins   bound to  interesting  phases of   project build lifecycle  We call these   instructions  project build lifecycle   mapping  or simply  lifecycle mapping    because they define how m2e maps   information from project pom xml file   to Eclipse workspace project   configuration and behaviour during   Eclipse workspace build       Project build lifecycle mapping   configuration can be specified in   project pom xml  contributed by   Eclipse plugins and there is also   default configuration for some   commonly used Maven plugins shipped   with m2e  We call these  lifecycle   mapping metadata sources   m2e will   create error marker like below for all   plugin executions that do not have   lifecycle mapping in any of the   mapping metadata sources   Plugin execution not covered by lifecycle configuration  org apache maven plugins maven-antrun-plugin 1 3 run     execution  generate-sources-input  phase  generate-sources        m2e matches plugin   executions to actions using   combination of plugin groupId    artifactId  version range and goal    There are three basic actions that m2e   can be instructed to do with a plugin   execution -- ignore  execute and   delegate to a project configurator

User · Answer

As an addendum to the previous answers -- there s a workaround I just discovered for if you can t or don t want to add all this boilerplate to your project POM  If you look in the following location    Eclipse folder  plugins org eclipse m2e lifecyclemapping defaults  m2e version    You should find a file called lifecycle-mapping-metadata xml where you can make the same changes described in the other answers and in M2E plugin execution not covered

User · Answer

I had the same problem with Eclipse nbsp v3 7  Indigo  and m2eclipse as my Maven plugin  The error was easily solved by explicitly stating the execution phase within the plugin definition  So my pom looks like this    lt project gt               lt build gt                       lt plugins gt               lt plugin gt                    lt groupId gt org codehaus mojo lt  groupId gt                   lt artifactId gt buildnumber-maven-plugin lt  artifactId gt                   lt version gt 1 0 lt  version gt                    lt configuration gt                       lt timestampFormat gt yyyy-MM-dd HH-mm-ss lt  timestampFormat gt                   lt  configuration gt                    lt executions gt                       lt execution gt                            lt phase gt post-clean lt  phase gt                            lt goals gt                               lt goal gt create-timestamp lt  goal gt                           lt  goals gt                       lt  execution gt                   lt  executions gt               lt  plugin gt           lt  plugins gt

User · Answer

Change the Maven preferences for plugin execution from error to ignore

User · Answer

I had this problem today  I was using STS 3 4 with its bundled Roo 1 2 4  Later I tried with Eclipse Kepler and Roo 1 2 5  same error   I ve changed my pom xml adding pluginTemplates tag after build and before plugins declaration but didn t work    What made the magic for me    Using jdk 1 7 0 51 Downloaded Roo 1 2 5 Downloaded Maven 3 2 1  if not  when executes  perform eclipse  this error appears  error 2  no such file or directory   Configured JDK  Roo and Maven bin directories on my PATH   export PATH  opt jdk1 7 0 51 bin  PATH export PATH  opt spring-roo-1 2 5 RELEASE bin  PATH export PATH  opt apache-maven-3 2 1 bin  PATH   Made my configuration as following   http   docs spring io spring-roo reference html beginning html     mkdir hello    cd hello   roo sh roo gt  project --topLevelPackage com foo roo gt  jpa setup --provider HIBERNATE --database HYPERSONIC PERSISTENT  roo gt  web mvc setup roo gt  perform eclipse   Open with Eclipse  nothing of STS  but I guess it works   Import -  Existing Projects into Workspace

User · Answer

In Eclipse Luna 4 4 0  you can chose to ignore this error in preferences  Window   Preferences   Maven   Errors Warnings   Plugin execution not covered by lifecycle configuration  Select Ignore   Warning   Error as you wish    Also  in the quick fix  Ctrl   1  for this error  it gives an option to  mark goal  as ignored in Eclipse build in Eclipse preferences  experimental   This is a cleaner way  as it doesn t modify your pom xml   You will need to do a Maven   Update project to fix the same error in any other project as well     In STS Spring-tool-suite   you can choose to ignore this error in preferences  Window   Preferences   Maven   Errors Warnings   Plugin execution not covered by life-cycle configuration  Select Ignore   Warning   Error as your wish  Then  Right click the project click Maven and update the project then error will gone

User · Answer

m2e 0 13 introduce a m2e connectors and m2e Market Place to extend m2e features  It s like the old m2e-extras repository   You can access the m2e market place from the preferences  Preferences Maven Discovery Open Catalog  Installing WTP integration solved most plugin issues for me

User · Answer

I ve had the same problem with indigo and a project that needs to generate Java sources from XSD   I could fix it by supplying the missing life-cycle mapping  as described on this page

User · Answer

I encountered exact the same problem with maven thrift plugin  Here s my solution which requires no need to mess up your pom xml    Use command line maven utility mvn     mvn eclipse eclipse   to create a eclipse project Import the project in eclipse  Remember to use      File   Import   General   Existing Projects into Workspace   to add the project into your workspace    This should fix the problem

User · Answer

Use m2e 0 12  last version from Sonatype

User · Answer

Instead of messing up your pom file  I would suggest you to go to Show View   Markers in Eclipse  select and delete the markers of appropriate errors

User · Answer

The error occurs when you use a life cycle phase that is not supported by the plugin  So the fix is to change the life cycle phase that works with the plugin

User · Answer

you can suppress this error in eclipse  Window -  Preferences -  Maven -  Error Warnings

User · Answer

I had the exact same problem after updating m2e and solved it by reinstalling Maven Integration for Eclipse WTP   As it turns out  I uninstalled it trying to update m2e from version 0 x to 1 x

User · Answer

I followed the GUI hint to finding any connector  and then I found AspectJ Integrator from SpringSource Team  After installation  it was settled

User · Answer

I could resolve this problem by using the Eclipse Plugin and updating the configuration and dependencies

User · Answer

If you are using Eclipse Juno  it could be the issue of Maven Integration For Eclipse WTP   So install the same from Eclipse Market Place   In Eclipse IDE  Help  Eclipse Market Place    type the query wtp and it will show maven integration for eclipse WTP for Juno  install it and update the maven dependencies and enjoy

User · Answer

This answer is just as good the top plugin-management answer above  which is to say  it s terrible    Just delete all the offending xml code in the pom   Done   Problem solved  except you just broke your maven config       Devs should be very careful they understand plugin-management tags before doing any of these solutions  Just slapping plugin-management around your plugins are random is likely to break the maven build for everyone else just to get eclipse to work

User · Answer

For me this was caused by AspectJ classes  I could not find a plugin under Discovery that could help  So  I fixed this by copying the org maven ide eclipse ajdt files  under plugin and feature folders  of an existing STS installation    I know  very rude approach

User · Answer

Where find WTP   Mouse down on  lt  plugin   in pom xml and  Discover new m2e connectors    I installed them all what are default checked and it works

User · Answer

Changing   lt artifactId gt aspectj-maven-plugin lt  artifactId gt   lt version gt 1 2 lt  version gt    into   lt artifactId gt aspectj-maven-plugin lt  artifactId gt   lt version gt 1 3 lt  version gt    solved the problem for me

User · Answer

I got the same error  After doing the following it went away     Right click on the project  Select Maven   Update Project

User · Answer

Note that the M2Eclipse  m2e  version 1 7 0 available in today s Eclipse Neon release train supports new syntax for specifying lifecycle mapping metadata  As a result boilerplate like this  here we re telling m2e to ignore the goal     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 codehaus mojo lt  groupId gt                   lt artifactId gt exec-maven-plugin lt  artifactId gt                   lt versionRange gt  1 5 0   lt  versionRange gt                   lt goals gt                     lt goal gt exec 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    can be replaced with a single line in the plugin s execution node    lt  m2e ignore  gt      See the release notes for details

User · Answer

This error happens also on neon because of missing m2e connector  Solution  hover error and select - Discover new m2e connectors   It will install new connector and that is it

User · Answer

I fixed it following blog post Upgrading Maven integration for SpringSource Tool Suite 2 8 0   Follow the advice on the section called  Uh oh   my projects no longer build   Even when it s intended for SpringSource Tool Suite I used it to fix a regular Eclipse installation  I didn t have to modify my pom files

User · Answer

Goto workspace rtc-ws  metadata  plugins org eclipse m2e core lifecycle-mapping-metadata xml then create lifecycle-mapping-metadata xml file and paste below and reload configuration as below  If you are using Eclipse 4 2 and have troubles with mapping and won t put mess into yours pom xml create new file lifecycle-mapping-metadata xml configure it in Windows - gt  Preferences - gt  Lifecycle mapping   don t forget press Reload workspace lifecycle mappings metadata after each change of this file    Here is example based on eclipse plugins org eclipse m2e lifecyclemapping defaults 1 2 0 20120903-1050 jar lifecycle-mapping-metadata xml   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 codehaus mojo lt  groupId gt                   lt artifactId gt buildnumber-maven-plugin lt  artifactId gt                   lt goals gt                       lt goal gt create-timestamp lt  goal gt                   lt  goals gt                   lt versionRange gt  0 0   lt  versionRange 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 apache maven plugins lt  groupId gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                   lt goals gt                       lt goal gt list lt  goal gt                   lt  goals gt                   lt versionRange gt  0 0   lt  versionRange 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 zeroturnaround lt  groupId gt                   lt artifactId gt jrebel-maven-plugin lt  artifactId gt                   lt goals gt                       lt goal gt generate lt  goal gt                   lt  goals gt                   lt versionRange gt  0 0   lt  versionRange 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 gwt-maven-plugin lt  artifactId gt                   lt goals gt                       lt goal gt compile lt  goal gt                   lt  goals gt                   lt versionRange gt  0 0   lt  versionRange 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 apache maven plugins lt  groupId gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                   lt goals gt                       lt goal gt copy-dependencies lt  goal gt                       lt goal gt unpack lt  goal gt                   lt  goals gt                   lt versionRange gt  0 0   lt  versionRange 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 apache maven plugins lt  groupId gt                   lt artifactId gt maven-antrun-plugin lt  artifactId gt                   lt versionRange gt  1 7   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 apache maven plugins lt  groupId gt                   lt artifactId gt maven-checkstyle-plugin lt  artifactId gt                   lt versionRange gt  2 8   lt  versionRange gt                   lt goals gt                       lt goal gt check 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

User · Answer

I was using    lt groupId gt org apache maven plugins lt  groupId gt   lt artifactId gt maven-antrun-plugin lt  artifactId gt   lt version gt 1 6 lt  version gt   lt executions gt       lt execution gt           lt id gt runSomeAntTasks lt  id gt           lt phase gt test-compile lt  phase gt                               lt goals gt               lt goal gt run lt  goal gt           lt  goals gt       lt  execution gt   lt  executions gt    and changed it to    lt groupId gt org apache maven plugins lt  groupId gt   lt artifactId gt maven-antrun-plugin lt  artifactId gt   lt version gt 1 6 lt  version gt   lt executions gt   lt execution gt       lt id gt runSomeAntTasks lt  id gt       lt phase gt integration-test lt  phase gt                                lt goals gt               lt goal gt run lt  goal gt           lt  goals gt       lt  execution gt   lt  executions gt    and the error went away   Maybe it s not recommended to bind an execution to the test-compile phase so finding a different phase might be an alternate solution to adding plugin-management configuration to the maven lifecycle

User · Answer

What a mess  I don t remember where I found this but I had to add the following to get M2Eclipse to be happy  Even more sad is that it isn t exactly easy to understand why this tag is needed    lt build gt            various plugins             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 codehaus mojo lt  groupId gt                                       lt artifactId gt aspectj-maven-plugin lt  artifactId gt                                       lt versionRange gt  1 0   lt  versionRange gt                                       lt goals gt                                           lt goal gt test-compile lt  goal gt                                           lt goal gt compile lt  goal gt                                       lt  goals gt                                   lt  pluginExecutionFilter gt                                   lt action gt                                       lt execute   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    There were a number of other issues with the M2Eclipse plug-in that simply didn t work with Spring Data  In the end I disabled M2Eclipse in favor of the Apache Eclipse plug-in

User · Answer

Suggested solution from Eclipse m2e documentation    Use quick-fix on the error in pom xml and select Permanently mark goal run in pom xml as ignored in Eclipse build - this will generate the required boilerplate code for you  To instruct Eclipse to run your plugin during build - just replace the  lt ignore  gt  tag with  lt execute  gt  tag in the generated configuration    lt action gt       lt execute  gt   lt  action gt    Alternatively you can instruct Eclipse to run the plugin on incremental builds as well    lt action gt       lt execute gt           lt runOnIncremental gt true lt  runOnIncremental gt       lt  execute  gt   lt  action gt

User · Answer

I encountered this using Eclipse nbsp v4 3  Kepler  and Maven 3 1   The solution is to use a JDK and not a JRE for your Eclipse project  Make sure to try maven clean and test from Eclipse just to download missing JAR files

User · Answer

I m meeting this problem for years    eclipse  shame  If your app is split into maven modules then you may consider removing affected modules from IDE  whenever you need to regenerate run the plugin use maven command line with install  eclipse is then happy with prepared artifacts present in your local repository  No fiddle-around needed

User · Answer

In my case of a similar problem  instead of using Andrew s suggestion for the fix  it worked simply after I introduced  lt pluginManagement gt  tag to the pom xml in question   Looks like that error is due to a missing  lt pluginManagement  tag   So  in order to avoid the exceptions in Eclipse  one needs to simply enclose all the plugin tags inside a  lt pluginManagement  tag  like so    lt build gt       lt pluginManagement gt           lt plugins gt               lt plugin gt       lt  plugin gt               lt plugin gt       lt  plugin gt                                  lt  plugins gt       lt  pluginManagement gt   lt  build gt    Once this structure is in place  the error goes away

User · Answer

Go to Help   Install New Software    Use this software repository  Make sure  Contact all update sites during install to find required software  is checked  Install the AJDT m2e Configurator   Source  Upgrading Maven integration for SpringSource Tool Suite 2 8 0  Andrew Eisenberg   This should automatically install ADJT if you don t have it installed  but if it doesn t  install AspectJ Development Tools  ADJT  first from  Indigo update site   according to your Eclipse version    More info on AspectJ Development Tools site

[eclipse] How to solve "Plugin execution not covered by lifecycle configuration" for Spring Data Maven Builds

Examples related to eclipse

Examples related to maven

Examples related to spring-data

Examples related to m2eclipse