Could not calculate build plan: Could not find artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3

Question

I'vea build error in Eclipse with m2eclipse plugin (version 0.12.0.20101115-1102):

Could not calculate build plan: Could not find artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3

I double checked and maven-resources-plugin is available in my local repository, as well as in Maven Repo.

Does anybody know what's wrong here ?

Solution 1

Seems to be gone with new Version (0.12.1) of m2eclipse plugin

Solution 2

Do you have the maven-resources-plugin defined in your project pom.xml?

<plugin>
  <groupid>org.apache.maven.plugins</groupid>
  <artifactid>maven-resources-plugin</artifactid>
  <version>2.4.3</version>
</plugin>

Even try deleting the folder from your local repository and let it download the jar again.

Solution 3

New to Maven, I also experienced this problem. The generic solution, as posted on Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved requires an add-on though, for developers who are still experiencing this problem, as it did not solve the problem for me. I've been struggling for more than an hour already and did the following to resolve the issue:

1. Ensure that Maven has been installed correctly. You can double check by running mvn --version via command prompt.
2. Close Eclipse
3. Delete all files in the repository folder (Users\$User$\.m2\repository)
4. Open Eclipse
5. Project > Clean > Clean All Projects > OK *Allow the clean to complete
6. Right click on project > Maven > Update Project
7. In the pop-up, ensure that "Update project configuration from pom.xml" and "Clean Projects" is ticked.
8. Click on Ok and allow Maven to reconfigure and download your project's plugins etc.

Note: I'm running Windows 8.1, using JDK 1.7, Maven 3.2.5 and Eclipse Juno.

Solution 4

I had to delete the folder from the local repository AND THEN restart eclipse. Just deleting the folder changed the error to a 401 denied for me and then a restart removed that next error completely.

Dean

View more solutions