m2e lifecycle-mapping not found

Question

I am trying to use the solution described here to solve the annoying  Plugin execution not covered by lifecycle configuration  org codehaus mojo build-helper-maven-plugin 1 7 add-source  execution  default  phase  generate-sources   when I place the following plugin on my pom xml    lt plugin gt   lt groupId gt org codehaus mojo lt  groupId gt   lt artifactId gt build-helper-maven-plugin lt  artifactId gt   lt executions gt       lt execution gt           lt phase gt generate-sources lt  phase gt           lt goals gt  lt goal gt add-source lt  goal gt  lt  goals gt           lt configuration gt               lt sources gt                   lt source gt src bootstrap java lt  source gt               lt  sources gt           lt  configuration gt       lt  execution gt   lt  executions gt   lt  plugin gt    But when I run mvn clean install I get this   Reason  POM  org eclipse m2e lifecycle-mapping  not found in repository  Unable to download the artifact from any repository  Does anyone have a clue on how to make m2e and maven happy

User · Answer

I have opened a  trivial  bug for this at m2e  Vote for it if you want the warning message to be gone for good     https   bugs eclipse org bugs show bug cgi id 367870

User · Answer

Try using the build pluginManagement section  e g      lt pluginManagement gt       lt plugins 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 bsc maven lt  groupId gt                                   lt artifactId gt maven-processor-plugin lt  artifactId gt                                   lt versionRange gt  2 0 2   lt  versionRange gt                                   lt goals gt                                       lt goal gt process 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    Here s an example to generate bundle manifest during incremental compilation inside Eclipse     lt build gt       lt pluginManagement gt           lt plugins 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 felix lt  groupId gt                                       lt artifactId gt maven-bundle-plugin lt  artifactId gt                                       lt versionRange gt  1 0 0   lt  versionRange gt                                       lt goals gt                                           lt goal gt manifest 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 plugins gt           lt plugin gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt version gt 2 3 2 lt  version gt               lt configuration gt                   lt source gt 1 6 lt  source gt                   lt target gt 1 6 lt  target gt                   lt encoding gt UTF-8 lt  encoding gt               lt  configuration gt           lt  plugin gt            lt plugin gt               lt groupId gt org apache felix lt  groupId gt               lt artifactId gt maven-bundle-plugin lt  artifactId gt               lt version gt 2 3 7 lt  version gt               lt extensions gt true lt  extensions gt               lt configuration gt                   lt instructions gt                   lt  instructions gt               lt  configuration gt               lt executions gt                   lt execution gt                       lt id gt manifest lt  id gt                       lt phase gt process-classes lt  phase gt                       lt goals gt                           lt goal gt manifest lt  goal gt                       lt  goals gt                   lt  execution gt               lt  executions gt           lt  plugin gt       lt  plugins gt   lt  build gt    versionRange is required  if omitted m2e  as of 1 1 0  will throw NullPointerException

User · Answer

I was  having the same issue  where   No marketplace entries found to handle build-helper-maven-plugin 1 8 add-source in Eclipse  Please see Help for more information   and clicking the Window   Preferences   Maven   Discovery   open catalog button would report no connection   Updating from 7u40 to 7u45 on Centos 6 4 and OSX fixes the issue

User · Answer

Maven is trying to download m2e s lifecycle-mapping artifact  which M2E uses to determine how to process plugins within Eclipse  adding source folders  etc     For some reason this artifact cannot be downloaded   Do you have an internet connection   Can other artifacts be downloaded from repositories   Proxy settings   For more details from Maven  try turning M2E debug output on  Settings Maven Debug Output checkbox  and it might give you more details as to why it cannot download from the repository

User · Answer

this step works on me    1  Remove your project on eclipse 2  Re import project 3  Delete target folder on your project 4  mvn or mvnw install

User · Answer

You can use this dummy plugin   mvn archetype generate -DgroupId org eclipse m2e -DartifactId lifecycle-mapping -Dversion 1 0 0 -DarchetypeArtifactId maven-archetype-mojo   After generating the project install deploy it

User · Answer

Here s how I do it  I put m2e s lifecycle-mapping plugin in a separate profile instead of the default  lt build gt  section  the profile is auto-activated during eclipse builds by presence of a m2e property  instead of manual activation in settings xml or otherwise   this will handle the m2e cases  while command-line maven will simply skip the profile and the m2e lifecycle-mapping plugin without any warnings  and everybody is happy    lt project gt           lt profiles gt               lt profile gt         lt id gt m2e lt  id gt         lt  -- This profile is only active when the property  m2e version          is set  which is the case when building in Eclipse with m2e  -- gt         lt activation gt           lt property gt             lt name gt m2e version lt  name gt           lt  property gt         lt  activation gt         lt build gt           lt pluginManagement gt             lt plugins 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     lt  groupId gt                           lt artifactId gt     lt  artifactId gt                           lt versionRange gt  0   lt  versionRange gt                           lt goals gt                             lt goal gt     lt  goal gt                           lt  goals gt                         lt  pluginExecutionFilter gt                         lt action gt                            lt  -- either  lt ignore gt  XOR  lt execute gt                             you must remove the other one  -- gt                            lt  -- execute  tells m2e to run the execution just like command-line maven                            from m2e s point of view  this is not recommended  because it is not                           deterministic and may make your eclipse unresponsive or behave strangely  -- gt                           lt execute gt                             lt  -- runOnIncremental  tells m2e to run the plugin-execution                             on each auto-build  true  or only on full-build  false   -- gt                             lt runOnIncremental gt false lt  runOnIncremental gt                           lt  execute gt                            lt  -- ignore  tells m2eclipse to skip the execution  -- 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       lt  profile gt             lt  profiles gt         lt  project gt

User · Answer

It happens due to a missing plugin configuration  as per vaadin s demo pom xml comment       This plugin s configuration is used to store Eclipse m2e settings   only  It has no influence on the Maven build itself     lt pluginManagement gt       lt plugins gt           lt  --This plugin s configuration is used to store Eclipse m2e ettings 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 com vaadin lt  groupId gt                                   lt artifactId gt                                      vaadin-maven-plugin                                  lt  artifactId gt                                   lt versionRange gt                                       7 1 5                                    lt  versionRange gt                                   lt goals gt                                       lt goal gt resources lt  goal gt                                       lt goal gt update-widgetset lt  goal gt                                       lt goal gt compile lt  goal gt                                       lt goal gt update-theme lt  goal gt                                       lt goal gt compile-theme 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

User · Answer

The org eclipse m2e lifecycle-mapping plugin doesn t exist actually  It should be used from the  lt build gt  lt pluginManagement gt  section of your pom xml  That way  it s not resolved by Maven but can be read by m2e   But a more practical solution to your problem would be to install the m2e build-helper connector in eclipse  You can install it from the Window   Preferences   Maven   Discovery   Open Catalog  That way build-helper-maven-plugin add-sources would be called in eclipse without having you to change your pom xml

User · Answer

Suprisingly these 3 steps helped me   mvn clean mvn package mvn spring-boot run

User · Answer

m2e 1 7 introduces a new syntax for lifecycle mapping metadata that doesn t cause this warning anymore    lt plugin gt   lt groupId gt org codehaus mojo lt  groupId gt   lt artifactId gt build-helper-maven-plugin lt  artifactId gt   lt executions gt       lt execution gt            lt  -- This executes the goal in Eclipse on project import               Other options like are available  eg ignore   -- gt           lt  m2e execute  gt            lt phase gt generate-sources lt  phase gt           lt goals gt  lt goal gt add-source lt  goal gt  lt  goals gt           lt configuration gt               lt sources gt                   lt source gt src bootstrap java lt  source gt               lt  sources gt           lt  configuration gt       lt  execution gt   lt  executions gt   lt  plugin gt

[maven-2] m2e lifecycle-mapping not found

Examples related to maven-2

Examples related to maven

Examples related to maven-plugin

Examples related to m2eclipse

Examples related to m2e