m2eclipse error

Question

I am developing a web application with Eclipse and I generate the project with a maven archetype   When I enable maven dependency management  Eclipse mark some errors in the pom file  this error is    Multiple annotations found at this line  - Execution default-testResources of goal org apache maven plugins maven-resources-          plugin 2 4 3 testResources failed    Plugin org apache maven plugins maven-resources-plugin 2 4 3 or one of its dependencies could not be resolved  Failed to collect   dependencies for org apache maven plugins maven-resources-plugin jar 2 4 3     org apache maven plugins maven-resources-  plugin 2 4 3 testResources default-testResources process-test-resources  - Plugin execution not covered by lifecycle configuration  org apache maven plugins maven-compiler-plugin 2 3 2 compile    execution  default-compile  phase  compile  - CoreException  Could not get the value for parameter compilerId for plugin execution default-compile    PluginResolutionException  Plugin org apache maven plugins maven-compiler-plugin 2 3 2 or one of its dependencies could not be   resolved  Failed to collect dependencies for org apache maven plugins maven-compiler-plugin jar 2 3 2       ArtifactDescriptorException  Failed to read artifact descriptor for org apache maven maven-plugin-api jar 2 0 6    ArtifactResolutionException  Failure to transfer org apache maven maven-plugin-api pom 2 0 6 from http   repo1 maven org   maven2 was cached in the local repository  resolution will not be reattempted until the update interval of central has elapsed or   updates are forced  Original error  Could not transfer artifact org apache maven maven-plugin-api pom 2 0 6 from to central  http     repo1 maven org maven2   null to http   repo1 maven org maven2 org apache maven maven-plugin-api 2 0 6 maven-plugin-  api-2 0 6 pom - CoreException  Could not get the value for parameter compilerId for plugin execution default-testCompile    PluginResolutionException  Plugin org apache maven plugins maven-compiler-plugin 2 3 2 or one of its dependencies could not be   resolved  Failed to collect dependencies for org apache maven plugins maven-compiler-plugin jar 2 3 2       ArtifactDescriptorException  Failed to read artifact descriptor for org apache maven maven-plugin-api jar 2 0 6    ArtifactResolutionException  Failure to transfer org apache maven maven-plugin-api pom 2 0 6 from http   repo1 maven org   maven2 was cached in the local repository  resolution will not be reattempted until the update interval of central has elapsed or   updates are forced  Original error  Could not transfer artifact org apache maven maven-plugin-api pom 2 0 6 from to central  http     repo1 maven org maven2   null to http   repo1 maven org maven2 org apache maven maven-plugin-api 2 0 6 maven-plugin-  api-2 0 6 pom - Execution default-resources of goal org apache maven plugins maven-resources-plugin 2 4 3 resources failed  Plugin   org apache maven plugins maven-resources-plugin 2 4 3 or one of its dependencies could not be resolved  Failed to collect   dependencies for org apache maven plugins maven-resources-plugin jar 2 4 3     org apache maven plugins maven-resources-  plugin 2 4 3 resources default-resources process-resources  - Plugin execution not covered by lifecycle configuration  org apache maven plugins maven-compiler-plugin   2 3 2 testCompile  execution  default-testCompile  phase  test-compile    My pom file is the following    lt project xmlns  http   maven apache org POM 4 0 0                  xmlns xsi  http   www w3 org 2001 XMLSchema-instance    xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org maven-v4 0 0 xsd  gt      lt modelVersion gt 4 0 0 lt  modelVersion gt      lt groupId gt com lala sarasa lt  groupId gt      lt artifactId gt msrdecision lt  artifactId gt     lt packaging gt war lt  packaging gt     lt version gt 1 0-SNAPSHOT lt  version gt     lt name gt msrdecision Maven Webapp lt  name gt     lt url gt http   maven apache org lt  url gt    lt dependencies gt      lt dependency gt        lt groupId gt junit lt  groupId gt         lt artifactId gt junit lt  artifactId gt         lt version gt 3 8 1 lt  version gt         lt scope gt test lt  scope gt       lt  dependency gt     lt  dependencies gt     lt build gt       lt finalName gt hello lt  finalName gt      lt  build gt    lt  project gt    Any idea

User · Answer

Encountered the same problem  For my case i was working behind a proxy   My solution was    Modify the settings xml file in the  m2 folder to add the proxy configuration                proxy       true       http       172 23 182 63       4145         In eclipse Click update settings button  Menu  Windows  Preferences  Maven  User Settings   Delete the  m2 repository folder Refresh my maven project    After step 4 - eclipse took a few minutes downloading files and project refreshed successfully

User · Answer

It must be a configuration problem  Your pom is fine    Here s what I did  New folder  put your pom inside  Then in eclipse  import -  maven -  existing maven project  Dependencies got included in the project    I did this using eclipse helios  I think the plugin version I am using is 0 12  You should check the maven properties in eclipse

User · Answer

This what helped me    Delete the project from eclipse  but don t delete from disk  Close eclipse In your user folder there is  m folder  Delete repository folder underneath it   m repository   Open eclipse Import project as existing maven project  from disk     Good luck

User · Answer

I am using MacOSX with Eclipse 4 3  Krepler   What I originally tried was to install Maven via the terminal using Brew  It installed correctly Maven 3 0 4  However when I tried to import any ready maven projects  File   Import   Maven  it would display the following two errors      No marketplace entries found to handle Execution default-testResources   What I did is go to Help   Eclipse Marketplace and type  Maven  in the search bar and install the first default Maven client for Eclipse  Everything worked for me from this point   Hope it helps to you too

User · Answer

Just go to your user folder  inside it there s a   m2  folder  open it and delete the folder  repository   Go to eclipse  clean your project  then right click- Maven- Update Project    and you are ready to go

User · Answer

The following steps worked for me    Close Eclipse  Navigate to user home directory   For example   C  Users YourUserName m2   Delete the  repository  folder  Re-open Eclipse  Click on the Maven project that has an issue and go to  Project  --   Clean   Right-click on the project and go to  Maven  --   Update Project      Close Eclipse  Open Eclipse  Click on the project folder in the  Project Explorer  window  usually on the left   Hit the  F5  key a few times to Refresh your project  Done  These steps worked for me in Eclipse Luna  Please let me know if I can help further

User · Answer

I also had same problem with Eclipse 3 7 2  Indigo  and maven 3 0 4   Eclipse wasn t picking up my maven settings  so this is what I did to fix the problem    Window - Preferences - Maven - Installations    Add   Maven 3 0 4 instead of using Embedded  Click Apply  amp  OK  Maven   Update Project Configuration    on project  right click  Shutdown Eclipse Run mvn install from the command line  Open Eclipse    Those steps worked for me  but the problem isn t consistent  I ve only had with issue on one computer

User · Answer

in my case there was a dependency without a version  in eclipse m2e does not force you to enter a version so i left it blank  once i put the version in pom xml from within eclipse all was fine

User · Answer

I had the same problem but with an other cause  The solution was to deactivate Avira Browser Protection  in german Browser-Schutz   I took the solusion from m2e cannot transfer metadata from nexus  but maven command line can  It can be activated again ones maven has the needed plugin

User · Answer

I solved this by running mvn -U install from command line and then  Maven- Update Project  from Eclipse

User · Answer

In this particular case  the solution was the right proxy configuration of eclipse  Window -  Preferences -  Network Connection   the company possessed a strict security system  I will leave the question  because there are answers that can help the community  Thank you very much for the answers above

User · Answer

I had same problem with Eclipse 3 7 2  Indigo  and maven 3 0 4   In my case  the problem was caused by missing maven-resources-plugin-2 4 3 jar in  user home   m2 repository org apache maven plugins maven-resources-plugin 2 4 3 folder   no idea why maven didn t update it   Solution   1   add dependency to pom xml   lt dependency gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-resources-plugin lt  artifactId gt       lt version gt 2 4 3 lt  version gt   lt  dependency gt    2   run mvn install from Eclipse or  from command line  3   refresh the project in eclipse  F5   4   run Maven  gt  Update Project Configuration    on project  right click   JAR file is downloaded to local repository and there are no errors in WS

User · Answer

My issue was that eclipse could not find the mvn bat file within the installation directory  The solution is to create a mvn bat file with the following code      dp0 mvn cmd       Save that file  Place it inside the  Maven Installation Folder  bin directory

User · Answer

This error bothered me for two days  I tried all kinds of solutions  nothing worked  Finally I give up and tried a radical approach  and it worked  Here are the steps    Save a copy of the pom xml   deleted all text in pom xml Let eclipse do a clean rebuild  of course everything will be broken   pasted back everything in the original pom xml let Eclipse build again   I guess it was  indeterministic  as the following article said    http   wiki eclipse org M2E plugin execution not covered

User · Answer

I had a similar case for the default groovy compiler plugin  The solution was to install ME2 provided by Springsource according to this answer  Plugin execution not covered by lifecycle configuration maven error  This immediately solved the  Plugin execution not covered by lifecycle configuration  problem in Eclispe Juno

User · Answer

In my case the problem was solved by Window -  Preferences -  Maven -  User Settings -  Update Settings  I don t know the problem cause at the first place

User · Answer

I would add some points that helped me to solve this problem     When all other missing archetypes have been indeed installed into your local repository  and the only remaining and abnormally sticking error is this  damned     one  whereas the maven-filtering-x jar is present in his directory  the problem could finally only be solved by creating a new work space as was suggested by Dan in his response   http   mail-archives apache org mod mbox incubator-isis-dev 201112 mbox  3CCALJOYLFfSJ5Xc z7a7N S2 kabuVv0ykv7A5afQaJJOb99iCdg mail gmail com 3E    thanks     Having the local repository OK  on the other hand  turned out to be quite costly  as many archetypes would not get loaded  due apparently to timeouts of m2eclipse and very unstable communication speeds in my case   In many cases only the error file could be found in the folder ex   xxx jar lastUpdated  instead of the jar or pom file  I had always to suppress this file to permit a new download   Also really worthy were     as already said  using the mvn clean install from the command line  apparently much more patient than m2eclipse  and also efficient and verbose  at least for the time being   and also the Update Project of the Maven menu  downloading using the dependency get goal   mvn org apache maven plugins maven-dependency-plugin 2 1 get -DrepoUrl url -Dartifact groupId artifactId version1    from within the project folder   hint given in another thread  thanks also     also downloading and installing manually   jar  sha1   from in particular   m2proxy  atlassian    adding other repositories in the pom xml itself  the settings xml mirror configuration did nt do the job  I don t know yet why   Ex   nexus content repositories releases  et nexus content repositories releases   sous repository jboss org  ou download java net maven 2     To finish  in any case  a lot of time       could have been et could certainly still be spared with a light tool repairing thoroughly the local repository straightaway  I could not yet find it  Actually it should even be normally a mvn command   --repair-local-repository

[eclipse] m2eclipse error

Examples related to eclipse

Examples related to maven

Examples related to m2eclipse