Failure to transfer dependency, was cached in the local repository

22,951

Solution 1

Problem fixed after deleting the .lastUpdated file and the dependency then downloading it again.

Solution 2

You can use -U parameter to force a check for the updated releases and snapshots on remote repositories, and resolve this issue.

Actually you can find this solution by using mvn -h to show Maven help.

Solution 3

Error occured because of old cache of Maven tool is present in your directory. So you must delete it. Go to C\User\"your user name"\m2 then delete it.

Share:
22,951
Mahmoud Saleh
Author by

Mahmoud Saleh

I am Mahmoud Saleh an Enthusiastic Software Engineer, Computer Science Graduate, Experienced in developing J2EE applications, Currently developing with Spring,JSF,Primefaces,Hibernate,Filenet. Email: [email protected] Linkedin: https://www.linkedin.com/in/mahmoud-saleh-60465545? Upwork: http://www.upwork.com/o/profiles/users/_~012a6a88e04dd2c1ed/

Updated on July 09, 2022

Comments

  • Mahmoud Saleh
    Mahmoud Saleh almost 2 years

    I am working on maven 2 project on eclipse, and I have the m2e plugin, and I am getting the following error in Eclipse:

    Failure to transfer com.thoughtworks.xstream:xstream:pom:1.3.1 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 com.thoughtworks.xstream:xstream:pom:1.3.1 from/to central (http://
     repo1.maven.org/maven2): Failed to create a selector. to http://repo1.maven.org/maven2/com/thoughtworks/xstream/
     xstream/1.3.1/xstream-1.3.1.pom
    

    please advise how to fix it.