m2eclipse error

Hi I am developing a web application with eclipse and I generate the project with a maven archetype. When I enable maven dependecy 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: <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"> <modelVersion>4.0.0</modelVersion> <groupId>com.lala.sarasa</groupId> <artifactId>msrdecision</artifactId> <packaging>war</packaging> <version>1.0-SNAPSHOT</version> <name>msrdecision Maven Webapp</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> <build> <finalName>hello</finalName> </build> </project> Any idea? Regards eclipse maven m2eclipse share|improve this question edited Apr 22 '12 at 14:37 Betlista 2,31011027 asked Jan 12 '12 at 12:05 McSas 7011925

The errors hint that maven can't reach a remote repository. Does "mvn clean package" work on the console? –  KarlsFriend Jan 12 '12 at 12:33 no don't work, same error –  McSas Jan 12 '12 at 12:40 1   my coworkers that use Windows are with same problem. I'm using ubuntu, same version of maven and eclipse, same project... and everything works fine... –  caarlos0 Apr 24 '12 at 18:04 add comment

12 Answers

activeoldestvotes

up vote0down vote	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. share|improve this answer answered Aug 13 '13 at 16:56 mohamed haseeb 112
	add comment

No problem. We won't show you that ad again. Why didn't you like it?

• Uninteresting
• Misleading
• Offensive
• Repetitive

Oops! I didn't mean to do this.

up vote0down vote	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. share|improve this answer answered Aug 11 '13 at 15:57 iuzuz 112
	add comment

up vote12down vote

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 & 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. share|improve this answer edited Jun 23 '13 at 15:27 sri 174 answered Aug 31 '12 at 16:22 Kyght 22623

add comment

up vote0down vote	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. share|improve this answer answered May 4 '13 at 16:48 simou 4452517
	add comment

up vote0down vote	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 share|improve this answer answered Apr 22 '13 at 23:40 no_answer_not_upvoted 3,23621443
	add comment

up vote0down vote

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 share|improve this answer answered Mar 26 '13 at 20:00 hli 112

add comment

up vote1down vote

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"). share|improve this answer edited Mar 10 '13 at 17:14 Krishnachandra Sharma 766625 answered Mar 10 '13 at 16:49 Laurent Chrétien 111

add comment

up vote0down vote

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. share|improve this answer edited Nov 9 '12 at 22:31 Ryan 10810 answered Jan 12 '12 at 12:26 KarlsFriend 33629

where are the maven properties in eclipse? –  McSas Jan 12 '12 at 12:32 I tried to put the pom file in a new folder. When I try to import the project eclipse show two erros: * No marketplace entries found to handle maven-compiler-plugin:2.3.2:testCompile in Eclipse. and * No marketplace entries found to handle maven-compiler-plugin:2.3.2:compile in Eclipse. // any idea? –  McSas Jan 12 '12 at 12:38 add comment

up vote7down vote

I solved this by running mvn -U install from command line and then "Maven->Update Project" from Eclipse share|improve this answer answered Nov 2 '12 at 8:39 altumano 933910

That solved my issue to, thanks! –  hithwen Jan 17 '13 at 16:12 1   I had to first edit the pom.xml file to add the dependency on the module that was causing the problem (org.apache.maven.plugins:maven-jar-plugin, in my case), then OUTSIDE OF ECLIPSE run mvn clean and then mvn -U install in the project folder. Then I restarted eclipse and did a clean/build on the project and All Was Well. –  Laura Apr 23 '13 at 12:44 add comment

up vote4down voteaccepted	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. share|improve this answer answered Jul 4 '12 at 12:12 McSas 7011925
	add comment

up vote3down vote	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. share|improve this answer answered Jun 29 '12 at 21:51 Kalaji 1415
	That solve my issue! Very nice. :) –  Jojas Mar 23 '13 at 8:21 solved my issue as well! thanks –  Iced_Earth Aug 1 '13 at 20:54 Solved my problem..Thanks..:) –  james Sep 28 '13 at 11:46 add comment

up vote27down vote

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 <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>2.4.3</version> </dependency> 2.) run mvn install from Eclipse or from command line 3.) refresh the project in eclipse (F5) 4.) run Maven > Update Project Configuration... on project (right click) JAR file is downloaded to local repository and there are no errors in WS. share|improve this answer edited Apr 25 '12 at 6:32 answered Mar 8 '12 at 12:52 Betlista 2,31011027

didn't work here... –  caarlos0 Apr 24 '12 at 18:04 did you checked that there is org\apache\maven\plugins\maven-resources-plugin\2.4.3 in repository ? –  Betlista Apr 24 '12 at 19:32 yep, 2.3, 2.4.3 and 2.5. Actually, after a lot of refreshes, mvn install eclipse:eclipse, cleans, close and reopen eclipse, it finally seem to work... but, it become with another error: "Unknow error". any idea? –  caarlos0 Apr 24 '12 at 20:14 Try to look into {eclipse.workspace}\.metadata\.log. –  Betlista Apr 25 '12 at 6:30