Could not transfer artifact org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to central (http://repo1.maven.org/maven2)










51















I have created a new maven project in SpringSource Tool Suite. I am getting this error in my new maven project.




Failure to transfer
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.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
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to
central (http://repo1.maven.org/maven2): Connect times out




pom.xml:



<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/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>com.test.app</groupId>
<artifactId>TestApp</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>TestApp</name>
<url>http://maven.apache.org</url>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>


Settings.xml



<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<pluginGroups>
</pluginGroups>
<proxies>
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>user</username>
<password>pass</password>
<host>ip</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
</proxies>
<servers>
</servers>
<mirrors>
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
</mirrors>
<profiles>
</profiles>
</settings>


Please note that I am able to build it.Error is showing in pom.xml inside IDE .Any solutions?










share|improve this question



















  • 6





    Are you behind the proxy?

    – Sam Rad
    Mar 11 '13 at 8:51











  • Do you need to set a proxy?

    – Derek
    Mar 11 '13 at 8:51






  • 1





    Are you sure you are not behind a proxy?

    – Anubhab
    Mar 11 '13 at 8:59






  • 1





    Show us the output of mvn help:effective-settings as well as your pom.xml.

    – carlspring
    Mar 11 '13 at 9:14






  • 1





    running it from IDE(STS)

    – Sajith
    Mar 11 '13 at 9:30















51















I have created a new maven project in SpringSource Tool Suite. I am getting this error in my new maven project.




Failure to transfer
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.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
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to
central (http://repo1.maven.org/maven2): Connect times out




pom.xml:



<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/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>com.test.app</groupId>
<artifactId>TestApp</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>TestApp</name>
<url>http://maven.apache.org</url>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>


Settings.xml



<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<pluginGroups>
</pluginGroups>
<proxies>
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>user</username>
<password>pass</password>
<host>ip</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
</proxies>
<servers>
</servers>
<mirrors>
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
</mirrors>
<profiles>
</profiles>
</settings>


Please note that I am able to build it.Error is showing in pom.xml inside IDE .Any solutions?










share|improve this question



















  • 6





    Are you behind the proxy?

    – Sam Rad
    Mar 11 '13 at 8:51











  • Do you need to set a proxy?

    – Derek
    Mar 11 '13 at 8:51






  • 1





    Are you sure you are not behind a proxy?

    – Anubhab
    Mar 11 '13 at 8:59






  • 1





    Show us the output of mvn help:effective-settings as well as your pom.xml.

    – carlspring
    Mar 11 '13 at 9:14






  • 1





    running it from IDE(STS)

    – Sajith
    Mar 11 '13 at 9:30













51












51








51


17






I have created a new maven project in SpringSource Tool Suite. I am getting this error in my new maven project.




Failure to transfer
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.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
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to
central (http://repo1.maven.org/maven2): Connect times out




pom.xml:



<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/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>com.test.app</groupId>
<artifactId>TestApp</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>TestApp</name>
<url>http://maven.apache.org</url>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>


Settings.xml



<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<pluginGroups>
</pluginGroups>
<proxies>
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>user</username>
<password>pass</password>
<host>ip</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
</proxies>
<servers>
</servers>
<mirrors>
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
</mirrors>
<profiles>
</profiles>
</settings>


Please note that I am able to build it.Error is showing in pom.xml inside IDE .Any solutions?










share|improve this question
















I have created a new maven project in SpringSource Tool Suite. I am getting this error in my new maven project.




Failure to transfer
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.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
org.apache.maven.plugins:maven-surefire-plugin:pom:2.7.1 from/to
central (http://repo1.maven.org/maven2): Connect times out




pom.xml:



<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/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>com.test.app</groupId>
<artifactId>TestApp</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>TestApp</name>
<url>http://maven.apache.org</url>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>


Settings.xml



<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<pluginGroups>
</pluginGroups>
<proxies>
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>user</username>
<password>pass</password>
<host>ip</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
</proxies>
<servers>
</servers>
<mirrors>
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
</mirrors>
<profiles>
</profiles>
</settings>


Please note that I am able to build it.Error is showing in pom.xml inside IDE .Any solutions?







java maven






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 8 '18 at 7:55









Naseer Mohammad

164212




164212










asked Mar 11 '13 at 8:50









SajithSajith

93261936




93261936







  • 6





    Are you behind the proxy?

    – Sam Rad
    Mar 11 '13 at 8:51











  • Do you need to set a proxy?

    – Derek
    Mar 11 '13 at 8:51






  • 1





    Are you sure you are not behind a proxy?

    – Anubhab
    Mar 11 '13 at 8:59






  • 1





    Show us the output of mvn help:effective-settings as well as your pom.xml.

    – carlspring
    Mar 11 '13 at 9:14






  • 1





    running it from IDE(STS)

    – Sajith
    Mar 11 '13 at 9:30












  • 6





    Are you behind the proxy?

    – Sam Rad
    Mar 11 '13 at 8:51











  • Do you need to set a proxy?

    – Derek
    Mar 11 '13 at 8:51






  • 1





    Are you sure you are not behind a proxy?

    – Anubhab
    Mar 11 '13 at 8:59






  • 1





    Show us the output of mvn help:effective-settings as well as your pom.xml.

    – carlspring
    Mar 11 '13 at 9:14






  • 1





    running it from IDE(STS)

    – Sajith
    Mar 11 '13 at 9:30







6




6





Are you behind the proxy?

– Sam Rad
Mar 11 '13 at 8:51





Are you behind the proxy?

– Sam Rad
Mar 11 '13 at 8:51













Do you need to set a proxy?

– Derek
Mar 11 '13 at 8:51





Do you need to set a proxy?

– Derek
Mar 11 '13 at 8:51




1




1





Are you sure you are not behind a proxy?

– Anubhab
Mar 11 '13 at 8:59





Are you sure you are not behind a proxy?

– Anubhab
Mar 11 '13 at 8:59




1




1





Show us the output of mvn help:effective-settings as well as your pom.xml.

– carlspring
Mar 11 '13 at 9:14





Show us the output of mvn help:effective-settings as well as your pom.xml.

– carlspring
Mar 11 '13 at 9:14




1




1





running it from IDE(STS)

– Sajith
Mar 11 '13 at 9:30





running it from IDE(STS)

– Sajith
Mar 11 '13 at 9:30












16 Answers
16






active

oldest

votes


















45














Simplify things by using the following settings.xml:



<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">

<proxies>
<proxy>
<id>myproxy</id>
<active>true</active>
<protocol>http</protocol>
<username>user</username> <!-- Put your username here -->
<password>pass</password> <!-- Put your password here -->
<host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
<port>80</port> <!-- Put your proxy server's port number here -->
<nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
</proxy>
</proxies>
</settings>


Under Linux/Unix, place it under ~/.m2/settings.xml. Under Windows place it under c:documents and settingsyouruser.m2settings.xml or c:usersyouruser.m2settings.xml.



You don't need the <mirrors/>, <profiles/> and <settings/> sections, unless you really know what they're for.






share|improve this answer























  • Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

    – Sajith
    Mar 11 '13 at 10:15






  • 1





    Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

    – carlspring
    Mar 11 '13 at 10:17












  • awesome. thanks

    – arn-arn
    Feb 29 '16 at 15:06


















43














This is solved for me when I update maven and check the option "Force update of Snapshots/Releases" in Eclipse. this clears all errors.
So right click on project -> Maven -> update project, then check the above option -> Ok.
Hope this helps you.






share|improve this answer




















  • 1





    This works for me, but I have to restart Eclipse.

    – ceklock
    Dec 8 '16 at 13:28







  • 1





    Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

    – Manoj
    Jan 22 '18 at 6:15






  • 1





    couldn't see this option in my versino of elcipse (photon)

    – weaveoftheride
    Sep 19 '18 at 9:18












  • Sometimes the address of the proxy has changed and we do not know.

    – Willy Makend
    Dec 11 '18 at 18:28


















22














It seems like your Maven is unable to connect to Maven repository at http://repo1.maven.org/maven2.



If you are using proxy and can access the link with browser the same settings need to be applied to Spring Source Tool Suite (if you are running within suite) or Maven.



For Maven proxy setting create a settings.xml in the .m2 directory with following details



<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<proxies>
<proxy>
<active>true</active>
<protocol>http</protocol>
<host>PROXY</host>
<port>3120</port>
<nonProxyHosts>maven</nonProxyHosts>
</proxy>
</proxies>
</settings>


If you are not using proxy and can access the link with browser, remove any proxy settings described above.






share|improve this answer
































    5














    For the first error you can simply clear your local repository cache to force it download from main repository rather than checking the local one.



    For second error, if you are behind proxy you should configure it this way Configuring a proxy otherwise you have a network problem now.






    share|improve this answer


















    • 1





      NP. Do you see the error in your POM or in Maven console?

      – Sam Rad
      Mar 11 '13 at 9:07







    • 1





      Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

      – Sajith
      Mar 11 '13 at 9:09











    • Would you edit your question to include your entire POM?

      – Sam Rad
      Mar 11 '13 at 9:12


















    5














    To me the solution was just deleted the specific folder which is giving the error from ~/.m2/repository/org/hsqldb/



    After deleting the hsqldb folder I have build the project and everything is fine.






    share|improve this answer























    • This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

      – Ankit
      Oct 7 '15 at 12:05


















    3














    What helped me were the suggestions by @carlspring (create a settings.xml to configure your http proxy):



    <?xml version="1.0" encoding="UTF-8"?>
    <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
    http://maven.apache.org/xsd/settings-1.0.0.xsd">

    <proxies>
    <proxy>
    <id>myproxy</id>
    <active>true</active>
    <protocol>http</protocol>
    <username>user</username> <!-- Put your username here -->
    <password>pass</password> <!-- Put your password here -->
    <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
    <port>80</port> <!-- Put your proxy server's port number here -->
    <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
    </proxy>
    </proxies>
    </settings>


    AND then refreshing eclipse project maven as suggested by @Peter T :



    "Force update of Snapshots/Releases" in Eclipse. this clears all errors. So right click on project -> Maven -> update project, then check the above option -> Ok. Hope this helps you.






    share|improve this answer






























      2














      It seems me there was a network issue. On your side, or on Maven side, or anywhere in the middle. Just try again later.



      If the error is permanent, check your network settings. If you are behind a proxy, you need the following in you ~/.m2/settings.xml:



      <proxies>
      <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
      </proxy>
      </proxies>





      share|improve this answer
































        2














        I strongly recommend to use a Maven Repository Manager such as Nexus. It will help you to get stable and reproducible builds with Maven. As the Repository Manager is usually in your LAN, you don't have to configure the proxy settings, but you need to define some other configurations:



        http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html



        http://maven.apache.org/repository-management.html






        share|improve this answer
































          2














          I started using maven on my machine first time in while. Got this error: Could not transfer artifact from/to central (https://repo.maven.apache.org/maven2) No such file or directory
          Cleaned up ~/.m2/repository directory. Don't experience this problem again






          share|improve this answer


















          • 1





            Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

            – Tobliug
            Oct 14 '16 at 13:57


















          1














          If you are in windows os and dont need any proxy
          then delete the whole proxy setting



          <proxies>
          <proxy>
          ..................
          </proxy>
          </proxies>


          and replace with



          <proxies/> 


          and then do a maven clean build






          share|improve this answer






























            1














            If none of the above works then try and go this question and answer:
            Maven error "Failure to transfer..."



            and delete your .lastUpdated files.






            share|improve this answer
































              1














              1. Update Maven Project and check the option "Force update of Snapshots/Releases", it will remove errors.

              2. If not, Maven clean and install the Project.

              3. Still the error isn't removed, repeat step 1.

              It worked for me :)






              share|improve this answer






























                1














                We have the Proxy set on company level.



                After disabling proxy in Internet Explorer this issue was solved (looks like it is then disabled on 'system' level), so all other browsers will pick this change too.



                Now I can issue MVN commands from CMD prompt and I have no problem while e.g.



                "Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-webapp/1.0/maven-archetype-webapp-1.0.pom"



                ...that was causing 'Build failure'



                Disabling proxy in IE needs to be done on daily basis in our case, because on each system start it gets set






                share|improve this answer






























                  1














                  This problem was solved by following steps -



                  1. Go to the local m2 repository and find the directory
                    org/apache/maven/plugins/maven-surefire-plugin.

                  2. Delete the problematic version.

                  3. maven update the project, then download it again.





                  share|improve this answer
































                    0














                    If you are not behind any proxy and still getting connection timeout error, please check firewall settings/ antivirus. Sometimes firewall may block the connectivity from any tool (like Eclipse/STS etc..)






                    share|improve this answer






























                      -3














                      First, You should check whether Maven tool is installed on your machine or not!!!






                      share|improve this answer





















                        protected by Mark Rotteveel Sep 23 '18 at 8:08



                        Thank you for your interest in this question.
                        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                        Would you like to answer one of these unanswered questions instead?














                        16 Answers
                        16






                        active

                        oldest

                        votes








                        16 Answers
                        16






                        active

                        oldest

                        votes









                        active

                        oldest

                        votes






                        active

                        oldest

                        votes









                        45














                        Simplify things by using the following settings.xml:



                        <?xml version="1.0" encoding="UTF-8"?>
                        <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                        http://maven.apache.org/xsd/settings-1.0.0.xsd">

                        <proxies>
                        <proxy>
                        <id>myproxy</id>
                        <active>true</active>
                        <protocol>http</protocol>
                        <username>user</username> <!-- Put your username here -->
                        <password>pass</password> <!-- Put your password here -->
                        <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                        <port>80</port> <!-- Put your proxy server's port number here -->
                        <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                        </proxy>
                        </proxies>
                        </settings>


                        Under Linux/Unix, place it under ~/.m2/settings.xml. Under Windows place it under c:documents and settingsyouruser.m2settings.xml or c:usersyouruser.m2settings.xml.



                        You don't need the <mirrors/>, <profiles/> and <settings/> sections, unless you really know what they're for.






                        share|improve this answer























                        • Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                          – Sajith
                          Mar 11 '13 at 10:15






                        • 1





                          Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                          – carlspring
                          Mar 11 '13 at 10:17












                        • awesome. thanks

                          – arn-arn
                          Feb 29 '16 at 15:06















                        45














                        Simplify things by using the following settings.xml:



                        <?xml version="1.0" encoding="UTF-8"?>
                        <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                        http://maven.apache.org/xsd/settings-1.0.0.xsd">

                        <proxies>
                        <proxy>
                        <id>myproxy</id>
                        <active>true</active>
                        <protocol>http</protocol>
                        <username>user</username> <!-- Put your username here -->
                        <password>pass</password> <!-- Put your password here -->
                        <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                        <port>80</port> <!-- Put your proxy server's port number here -->
                        <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                        </proxy>
                        </proxies>
                        </settings>


                        Under Linux/Unix, place it under ~/.m2/settings.xml. Under Windows place it under c:documents and settingsyouruser.m2settings.xml or c:usersyouruser.m2settings.xml.



                        You don't need the <mirrors/>, <profiles/> and <settings/> sections, unless you really know what they're for.






                        share|improve this answer























                        • Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                          – Sajith
                          Mar 11 '13 at 10:15






                        • 1





                          Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                          – carlspring
                          Mar 11 '13 at 10:17












                        • awesome. thanks

                          – arn-arn
                          Feb 29 '16 at 15:06













                        45












                        45








                        45







                        Simplify things by using the following settings.xml:



                        <?xml version="1.0" encoding="UTF-8"?>
                        <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                        http://maven.apache.org/xsd/settings-1.0.0.xsd">

                        <proxies>
                        <proxy>
                        <id>myproxy</id>
                        <active>true</active>
                        <protocol>http</protocol>
                        <username>user</username> <!-- Put your username here -->
                        <password>pass</password> <!-- Put your password here -->
                        <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                        <port>80</port> <!-- Put your proxy server's port number here -->
                        <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                        </proxy>
                        </proxies>
                        </settings>


                        Under Linux/Unix, place it under ~/.m2/settings.xml. Under Windows place it under c:documents and settingsyouruser.m2settings.xml or c:usersyouruser.m2settings.xml.



                        You don't need the <mirrors/>, <profiles/> and <settings/> sections, unless you really know what they're for.






                        share|improve this answer













                        Simplify things by using the following settings.xml:



                        <?xml version="1.0" encoding="UTF-8"?>
                        <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                        http://maven.apache.org/xsd/settings-1.0.0.xsd">

                        <proxies>
                        <proxy>
                        <id>myproxy</id>
                        <active>true</active>
                        <protocol>http</protocol>
                        <username>user</username> <!-- Put your username here -->
                        <password>pass</password> <!-- Put your password here -->
                        <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                        <port>80</port> <!-- Put your proxy server's port number here -->
                        <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                        </proxy>
                        </proxies>
                        </settings>


                        Under Linux/Unix, place it under ~/.m2/settings.xml. Under Windows place it under c:documents and settingsyouruser.m2settings.xml or c:usersyouruser.m2settings.xml.



                        You don't need the <mirrors/>, <profiles/> and <settings/> sections, unless you really know what they're for.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Mar 11 '13 at 10:06









                        carlspringcarlspring

                        18.4k1879152




                        18.4k1879152












                        • Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                          – Sajith
                          Mar 11 '13 at 10:15






                        • 1





                          Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                          – carlspring
                          Mar 11 '13 at 10:17












                        • awesome. thanks

                          – arn-arn
                          Feb 29 '16 at 15:06

















                        • Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                          – Sajith
                          Mar 11 '13 at 10:15






                        • 1





                          Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                          – carlspring
                          Mar 11 '13 at 10:17












                        • awesome. thanks

                          – arn-arn
                          Feb 29 '16 at 15:06
















                        Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                        – Sajith
                        Mar 11 '13 at 10:15





                        Thanks for helping.But still getting same error.Note that I am able to build it .error is only in the IDE.

                        – Sajith
                        Mar 11 '13 at 10:15




                        1




                        1





                        Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                        – carlspring
                        Mar 11 '13 at 10:17






                        Okay, then. In your IDE make sure it's pointing to the same settings.xml file, as your proxy settings are not getting picked up by your IDE apparently.

                        – carlspring
                        Mar 11 '13 at 10:17














                        awesome. thanks

                        – arn-arn
                        Feb 29 '16 at 15:06





                        awesome. thanks

                        – arn-arn
                        Feb 29 '16 at 15:06













                        43














                        This is solved for me when I update maven and check the option "Force update of Snapshots/Releases" in Eclipse. this clears all errors.
                        So right click on project -> Maven -> update project, then check the above option -> Ok.
                        Hope this helps you.






                        share|improve this answer




















                        • 1





                          This works for me, but I have to restart Eclipse.

                          – ceklock
                          Dec 8 '16 at 13:28







                        • 1





                          Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                          – Manoj
                          Jan 22 '18 at 6:15






                        • 1





                          couldn't see this option in my versino of elcipse (photon)

                          – weaveoftheride
                          Sep 19 '18 at 9:18












                        • Sometimes the address of the proxy has changed and we do not know.

                          – Willy Makend
                          Dec 11 '18 at 18:28















                        43














                        This is solved for me when I update maven and check the option "Force update of Snapshots/Releases" in Eclipse. this clears all errors.
                        So right click on project -> Maven -> update project, then check the above option -> Ok.
                        Hope this helps you.






                        share|improve this answer




















                        • 1





                          This works for me, but I have to restart Eclipse.

                          – ceklock
                          Dec 8 '16 at 13:28







                        • 1





                          Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                          – Manoj
                          Jan 22 '18 at 6:15






                        • 1





                          couldn't see this option in my versino of elcipse (photon)

                          – weaveoftheride
                          Sep 19 '18 at 9:18












                        • Sometimes the address of the proxy has changed and we do not know.

                          – Willy Makend
                          Dec 11 '18 at 18:28













                        43












                        43








                        43







                        This is solved for me when I update maven and check the option "Force update of Snapshots/Releases" in Eclipse. this clears all errors.
                        So right click on project -> Maven -> update project, then check the above option -> Ok.
                        Hope this helps you.






                        share|improve this answer















                        This is solved for me when I update maven and check the option "Force update of Snapshots/Releases" in Eclipse. this clears all errors.
                        So right click on project -> Maven -> update project, then check the above option -> Ok.
                        Hope this helps you.







                        share|improve this answer














                        share|improve this answer



                        share|improve this answer








                        edited Dec 4 '18 at 10:12

























                        answered May 27 '14 at 10:36









                        Peter T.Peter T.

                        5,37722428




                        5,37722428







                        • 1





                          This works for me, but I have to restart Eclipse.

                          – ceklock
                          Dec 8 '16 at 13:28







                        • 1





                          Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                          – Manoj
                          Jan 22 '18 at 6:15






                        • 1





                          couldn't see this option in my versino of elcipse (photon)

                          – weaveoftheride
                          Sep 19 '18 at 9:18












                        • Sometimes the address of the proxy has changed and we do not know.

                          – Willy Makend
                          Dec 11 '18 at 18:28












                        • 1





                          This works for me, but I have to restart Eclipse.

                          – ceklock
                          Dec 8 '16 at 13:28







                        • 1





                          Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                          – Manoj
                          Jan 22 '18 at 6:15






                        • 1





                          couldn't see this option in my versino of elcipse (photon)

                          – weaveoftheride
                          Sep 19 '18 at 9:18












                        • Sometimes the address of the proxy has changed and we do not know.

                          – Willy Makend
                          Dec 11 '18 at 18:28







                        1




                        1





                        This works for me, but I have to restart Eclipse.

                        – ceklock
                        Dec 8 '16 at 13:28






                        This works for me, but I have to restart Eclipse.

                        – ceklock
                        Dec 8 '16 at 13:28





                        1




                        1





                        Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                        – Manoj
                        Jan 22 '18 at 6:15





                        Thanks it worked for me. I copied eclipse from one machine to another and the maven local cache seems to be the issue behind it for me. When I updated the sanpshot, it worked for me.

                        – Manoj
                        Jan 22 '18 at 6:15




                        1




                        1





                        couldn't see this option in my versino of elcipse (photon)

                        – weaveoftheride
                        Sep 19 '18 at 9:18






                        couldn't see this option in my versino of elcipse (photon)

                        – weaveoftheride
                        Sep 19 '18 at 9:18














                        Sometimes the address of the proxy has changed and we do not know.

                        – Willy Makend
                        Dec 11 '18 at 18:28





                        Sometimes the address of the proxy has changed and we do not know.

                        – Willy Makend
                        Dec 11 '18 at 18:28











                        22














                        It seems like your Maven is unable to connect to Maven repository at http://repo1.maven.org/maven2.



                        If you are using proxy and can access the link with browser the same settings need to be applied to Spring Source Tool Suite (if you are running within suite) or Maven.



                        For Maven proxy setting create a settings.xml in the .m2 directory with following details



                        <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                        http://maven.apache.org/xsd/settings-1.0.0.xsd">
                        <proxies>
                        <proxy>
                        <active>true</active>
                        <protocol>http</protocol>
                        <host>PROXY</host>
                        <port>3120</port>
                        <nonProxyHosts>maven</nonProxyHosts>
                        </proxy>
                        </proxies>
                        </settings>


                        If you are not using proxy and can access the link with browser, remove any proxy settings described above.






                        share|improve this answer





























                          22














                          It seems like your Maven is unable to connect to Maven repository at http://repo1.maven.org/maven2.



                          If you are using proxy and can access the link with browser the same settings need to be applied to Spring Source Tool Suite (if you are running within suite) or Maven.



                          For Maven proxy setting create a settings.xml in the .m2 directory with following details



                          <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                          http://maven.apache.org/xsd/settings-1.0.0.xsd">
                          <proxies>
                          <proxy>
                          <active>true</active>
                          <protocol>http</protocol>
                          <host>PROXY</host>
                          <port>3120</port>
                          <nonProxyHosts>maven</nonProxyHosts>
                          </proxy>
                          </proxies>
                          </settings>


                          If you are not using proxy and can access the link with browser, remove any proxy settings described above.






                          share|improve this answer



























                            22












                            22








                            22







                            It seems like your Maven is unable to connect to Maven repository at http://repo1.maven.org/maven2.



                            If you are using proxy and can access the link with browser the same settings need to be applied to Spring Source Tool Suite (if you are running within suite) or Maven.



                            For Maven proxy setting create a settings.xml in the .m2 directory with following details



                            <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                            xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                            http://maven.apache.org/xsd/settings-1.0.0.xsd">
                            <proxies>
                            <proxy>
                            <active>true</active>
                            <protocol>http</protocol>
                            <host>PROXY</host>
                            <port>3120</port>
                            <nonProxyHosts>maven</nonProxyHosts>
                            </proxy>
                            </proxies>
                            </settings>


                            If you are not using proxy and can access the link with browser, remove any proxy settings described above.






                            share|improve this answer















                            It seems like your Maven is unable to connect to Maven repository at http://repo1.maven.org/maven2.



                            If you are using proxy and can access the link with browser the same settings need to be applied to Spring Source Tool Suite (if you are running within suite) or Maven.



                            For Maven proxy setting create a settings.xml in the .m2 directory with following details



                            <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                            xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                            http://maven.apache.org/xsd/settings-1.0.0.xsd">
                            <proxies>
                            <proxy>
                            <active>true</active>
                            <protocol>http</protocol>
                            <host>PROXY</host>
                            <port>3120</port>
                            <nonProxyHosts>maven</nonProxyHosts>
                            </proxy>
                            </proxies>
                            </settings>


                            If you are not using proxy and can access the link with browser, remove any proxy settings described above.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Apr 6 '18 at 11:58









                            Lii

                            7,24744163




                            7,24744163










                            answered Mar 11 '13 at 9:05









                            Uday ShankarUday Shankar

                            689417




                            689417





















                                5














                                For the first error you can simply clear your local repository cache to force it download from main repository rather than checking the local one.



                                For second error, if you are behind proxy you should configure it this way Configuring a proxy otherwise you have a network problem now.






                                share|improve this answer


















                                • 1





                                  NP. Do you see the error in your POM or in Maven console?

                                  – Sam Rad
                                  Mar 11 '13 at 9:07







                                • 1





                                  Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                  – Sajith
                                  Mar 11 '13 at 9:09











                                • Would you edit your question to include your entire POM?

                                  – Sam Rad
                                  Mar 11 '13 at 9:12















                                5














                                For the first error you can simply clear your local repository cache to force it download from main repository rather than checking the local one.



                                For second error, if you are behind proxy you should configure it this way Configuring a proxy otherwise you have a network problem now.






                                share|improve this answer


















                                • 1





                                  NP. Do you see the error in your POM or in Maven console?

                                  – Sam Rad
                                  Mar 11 '13 at 9:07







                                • 1





                                  Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                  – Sajith
                                  Mar 11 '13 at 9:09











                                • Would you edit your question to include your entire POM?

                                  – Sam Rad
                                  Mar 11 '13 at 9:12













                                5












                                5








                                5







                                For the first error you can simply clear your local repository cache to force it download from main repository rather than checking the local one.



                                For second error, if you are behind proxy you should configure it this way Configuring a proxy otherwise you have a network problem now.






                                share|improve this answer













                                For the first error you can simply clear your local repository cache to force it download from main repository rather than checking the local one.



                                For second error, if you are behind proxy you should configure it this way Configuring a proxy otherwise you have a network problem now.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Mar 11 '13 at 8:56









                                Sam RadSam Rad

                                8,28552645




                                8,28552645







                                • 1





                                  NP. Do you see the error in your POM or in Maven console?

                                  – Sam Rad
                                  Mar 11 '13 at 9:07







                                • 1





                                  Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                  – Sajith
                                  Mar 11 '13 at 9:09











                                • Would you edit your question to include your entire POM?

                                  – Sam Rad
                                  Mar 11 '13 at 9:12












                                • 1





                                  NP. Do you see the error in your POM or in Maven console?

                                  – Sam Rad
                                  Mar 11 '13 at 9:07







                                • 1





                                  Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                  – Sajith
                                  Mar 11 '13 at 9:09











                                • Would you edit your question to include your entire POM?

                                  – Sam Rad
                                  Mar 11 '13 at 9:12







                                1




                                1





                                NP. Do you see the error in your POM or in Maven console?

                                – Sam Rad
                                Mar 11 '13 at 9:07






                                NP. Do you see the error in your POM or in Maven console?

                                – Sam Rad
                                Mar 11 '13 at 9:07





                                1




                                1





                                Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                – Sajith
                                Mar 11 '13 at 9:09





                                Error is showing in pom.xml .<project xmlns="maven.apache.org/POM/4.0.0" xmlns:xsi="w3.org/2001/XMLSchema-instance" xsi:schemaLocation="maven.apache.org/POM/4.0.0 maven.apache.org/xsd/maven-4.0.0.xsd">

                                – Sajith
                                Mar 11 '13 at 9:09













                                Would you edit your question to include your entire POM?

                                – Sam Rad
                                Mar 11 '13 at 9:12





                                Would you edit your question to include your entire POM?

                                – Sam Rad
                                Mar 11 '13 at 9:12











                                5














                                To me the solution was just deleted the specific folder which is giving the error from ~/.m2/repository/org/hsqldb/



                                After deleting the hsqldb folder I have build the project and everything is fine.






                                share|improve this answer























                                • This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                  – Ankit
                                  Oct 7 '15 at 12:05















                                5














                                To me the solution was just deleted the specific folder which is giving the error from ~/.m2/repository/org/hsqldb/



                                After deleting the hsqldb folder I have build the project and everything is fine.






                                share|improve this answer























                                • This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                  – Ankit
                                  Oct 7 '15 at 12:05













                                5












                                5








                                5







                                To me the solution was just deleted the specific folder which is giving the error from ~/.m2/repository/org/hsqldb/



                                After deleting the hsqldb folder I have build the project and everything is fine.






                                share|improve this answer













                                To me the solution was just deleted the specific folder which is giving the error from ~/.m2/repository/org/hsqldb/



                                After deleting the hsqldb folder I have build the project and everything is fine.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Aug 25 '15 at 11:46









                                Ali786Ali786

                                2,61212749




                                2,61212749












                                • This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                  – Ankit
                                  Oct 7 '15 at 12:05

















                                • This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                  – Ankit
                                  Oct 7 '15 at 12:05
















                                This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                – Ankit
                                Oct 7 '15 at 12:05





                                This worked for me too. I am using STS. Nothing else worked like Maven-update-force... or settings.xml. In my case the reported error was for maven-surefire-plugin. I deleted this folder which was located at .m2/repository/apache/org/maven/plugins/maven-plugins. After that I cleaned the project and it removed the error in pom.xml

                                – Ankit
                                Oct 7 '15 at 12:05











                                3














                                What helped me were the suggestions by @carlspring (create a settings.xml to configure your http proxy):



                                <?xml version="1.0" encoding="UTF-8"?>
                                <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                                http://maven.apache.org/xsd/settings-1.0.0.xsd">

                                <proxies>
                                <proxy>
                                <id>myproxy</id>
                                <active>true</active>
                                <protocol>http</protocol>
                                <username>user</username> <!-- Put your username here -->
                                <password>pass</password> <!-- Put your password here -->
                                <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                                <port>80</port> <!-- Put your proxy server's port number here -->
                                <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                                </proxy>
                                </proxies>
                                </settings>


                                AND then refreshing eclipse project maven as suggested by @Peter T :



                                "Force update of Snapshots/Releases" in Eclipse. this clears all errors. So right click on project -> Maven -> update project, then check the above option -> Ok. Hope this helps you.






                                share|improve this answer



























                                  3














                                  What helped me were the suggestions by @carlspring (create a settings.xml to configure your http proxy):



                                  <?xml version="1.0" encoding="UTF-8"?>
                                  <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                                  http://maven.apache.org/xsd/settings-1.0.0.xsd">

                                  <proxies>
                                  <proxy>
                                  <id>myproxy</id>
                                  <active>true</active>
                                  <protocol>http</protocol>
                                  <username>user</username> <!-- Put your username here -->
                                  <password>pass</password> <!-- Put your password here -->
                                  <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                                  <port>80</port> <!-- Put your proxy server's port number here -->
                                  <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                                  </proxy>
                                  </proxies>
                                  </settings>


                                  AND then refreshing eclipse project maven as suggested by @Peter T :



                                  "Force update of Snapshots/Releases" in Eclipse. this clears all errors. So right click on project -> Maven -> update project, then check the above option -> Ok. Hope this helps you.






                                  share|improve this answer

























                                    3












                                    3








                                    3







                                    What helped me were the suggestions by @carlspring (create a settings.xml to configure your http proxy):



                                    <?xml version="1.0" encoding="UTF-8"?>
                                    <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                    xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                                    http://maven.apache.org/xsd/settings-1.0.0.xsd">

                                    <proxies>
                                    <proxy>
                                    <id>myproxy</id>
                                    <active>true</active>
                                    <protocol>http</protocol>
                                    <username>user</username> <!-- Put your username here -->
                                    <password>pass</password> <!-- Put your password here -->
                                    <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                                    <port>80</port> <!-- Put your proxy server's port number here -->
                                    <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                                    </proxy>
                                    </proxies>
                                    </settings>


                                    AND then refreshing eclipse project maven as suggested by @Peter T :



                                    "Force update of Snapshots/Releases" in Eclipse. this clears all errors. So right click on project -> Maven -> update project, then check the above option -> Ok. Hope this helps you.






                                    share|improve this answer













                                    What helped me were the suggestions by @carlspring (create a settings.xml to configure your http proxy):



                                    <?xml version="1.0" encoding="UTF-8"?>
                                    <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
                                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                    xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                                    http://maven.apache.org/xsd/settings-1.0.0.xsd">

                                    <proxies>
                                    <proxy>
                                    <id>myproxy</id>
                                    <active>true</active>
                                    <protocol>http</protocol>
                                    <username>user</username> <!-- Put your username here -->
                                    <password>pass</password> <!-- Put your password here -->
                                    <host>123.45.6.78</host> <!-- Put the IP address of your proxy server here -->
                                    <port>80</port> <!-- Put your proxy server's port number here -->
                                    <nonProxyHosts>local.net|some.host.com</nonProxyHosts> <!-- Do not use this setting unless you know what you're doing. -->
                                    </proxy>
                                    </proxies>
                                    </settings>


                                    AND then refreshing eclipse project maven as suggested by @Peter T :



                                    "Force update of Snapshots/Releases" in Eclipse. this clears all errors. So right click on project -> Maven -> update project, then check the above option -> Ok. Hope this helps you.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Apr 12 '16 at 23:29









                                    vsmvsm

                                    477




                                    477





















                                        2














                                        It seems me there was a network issue. On your side, or on Maven side, or anywhere in the middle. Just try again later.



                                        If the error is permanent, check your network settings. If you are behind a proxy, you need the following in you ~/.m2/settings.xml:



                                        <proxies>
                                        <proxy>
                                        <id>optional</id>
                                        <active>true</active>
                                        <protocol>http</protocol>
                                        <username>proxyuser</username>
                                        <password>proxypass</password>
                                        <host>proxy.host.net</host>
                                        <port>80</port>
                                        <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
                                        </proxy>
                                        </proxies>





                                        share|improve this answer





























                                          2














                                          It seems me there was a network issue. On your side, or on Maven side, or anywhere in the middle. Just try again later.



                                          If the error is permanent, check your network settings. If you are behind a proxy, you need the following in you ~/.m2/settings.xml:



                                          <proxies>
                                          <proxy>
                                          <id>optional</id>
                                          <active>true</active>
                                          <protocol>http</protocol>
                                          <username>proxyuser</username>
                                          <password>proxypass</password>
                                          <host>proxy.host.net</host>
                                          <port>80</port>
                                          <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
                                          </proxy>
                                          </proxies>





                                          share|improve this answer



























                                            2












                                            2








                                            2







                                            It seems me there was a network issue. On your side, or on Maven side, or anywhere in the middle. Just try again later.



                                            If the error is permanent, check your network settings. If you are behind a proxy, you need the following in you ~/.m2/settings.xml:



                                            <proxies>
                                            <proxy>
                                            <id>optional</id>
                                            <active>true</active>
                                            <protocol>http</protocol>
                                            <username>proxyuser</username>
                                            <password>proxypass</password>
                                            <host>proxy.host.net</host>
                                            <port>80</port>
                                            <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
                                            </proxy>
                                            </proxies>





                                            share|improve this answer















                                            It seems me there was a network issue. On your side, or on Maven side, or anywhere in the middle. Just try again later.



                                            If the error is permanent, check your network settings. If you are behind a proxy, you need the following in you ~/.m2/settings.xml:



                                            <proxies>
                                            <proxy>
                                            <id>optional</id>
                                            <active>true</active>
                                            <protocol>http</protocol>
                                            <username>proxyuser</username>
                                            <password>proxypass</password>
                                            <host>proxy.host.net</host>
                                            <port>80</port>
                                            <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
                                            </proxy>
                                            </proxies>






                                            share|improve this answer














                                            share|improve this answer



                                            share|improve this answer








                                            edited Mar 11 '13 at 8:59

























                                            answered Mar 11 '13 at 8:53









                                            Etienne MiretEtienne Miret

                                            4,76021729




                                            4,76021729





















                                                2














                                                I strongly recommend to use a Maven Repository Manager such as Nexus. It will help you to get stable and reproducible builds with Maven. As the Repository Manager is usually in your LAN, you don't have to configure the proxy settings, but you need to define some other configurations:



                                                http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html



                                                http://maven.apache.org/repository-management.html






                                                share|improve this answer





























                                                  2














                                                  I strongly recommend to use a Maven Repository Manager such as Nexus. It will help you to get stable and reproducible builds with Maven. As the Repository Manager is usually in your LAN, you don't have to configure the proxy settings, but you need to define some other configurations:



                                                  http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html



                                                  http://maven.apache.org/repository-management.html






                                                  share|improve this answer



























                                                    2












                                                    2








                                                    2







                                                    I strongly recommend to use a Maven Repository Manager such as Nexus. It will help you to get stable and reproducible builds with Maven. As the Repository Manager is usually in your LAN, you don't have to configure the proxy settings, but you need to define some other configurations:



                                                    http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html



                                                    http://maven.apache.org/repository-management.html






                                                    share|improve this answer















                                                    I strongly recommend to use a Maven Repository Manager such as Nexus. It will help you to get stable and reproducible builds with Maven. As the Repository Manager is usually in your LAN, you don't have to configure the proxy settings, but you need to define some other configurations:



                                                    http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html



                                                    http://maven.apache.org/repository-management.html







                                                    share|improve this answer














                                                    share|improve this answer



                                                    share|improve this answer








                                                    edited Mar 11 '13 at 9:13

























                                                    answered Mar 11 '13 at 9:03









                                                    PucePuce

                                                    28.1k955112




                                                    28.1k955112





















                                                        2














                                                        I started using maven on my machine first time in while. Got this error: Could not transfer artifact from/to central (https://repo.maven.apache.org/maven2) No such file or directory
                                                        Cleaned up ~/.m2/repository directory. Don't experience this problem again






                                                        share|improve this answer


















                                                        • 1





                                                          Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                          – Tobliug
                                                          Oct 14 '16 at 13:57















                                                        2














                                                        I started using maven on my machine first time in while. Got this error: Could not transfer artifact from/to central (https://repo.maven.apache.org/maven2) No such file or directory
                                                        Cleaned up ~/.m2/repository directory. Don't experience this problem again






                                                        share|improve this answer


















                                                        • 1





                                                          Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                          – Tobliug
                                                          Oct 14 '16 at 13:57













                                                        2












                                                        2








                                                        2







                                                        I started using maven on my machine first time in while. Got this error: Could not transfer artifact from/to central (https://repo.maven.apache.org/maven2) No such file or directory
                                                        Cleaned up ~/.m2/repository directory. Don't experience this problem again






                                                        share|improve this answer













                                                        I started using maven on my machine first time in while. Got this error: Could not transfer artifact from/to central (https://repo.maven.apache.org/maven2) No such file or directory
                                                        Cleaned up ~/.m2/repository directory. Don't experience this problem again







                                                        share|improve this answer












                                                        share|improve this answer



                                                        share|improve this answer










                                                        answered Sep 22 '16 at 4:31









                                                        thepolinathepolina

                                                        544720




                                                        544720







                                                        • 1





                                                          Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                          – Tobliug
                                                          Oct 14 '16 at 13:57












                                                        • 1





                                                          Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                          – Tobliug
                                                          Oct 14 '16 at 13:57







                                                        1




                                                        1





                                                        Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                        – Tobliug
                                                        Oct 14 '16 at 13:57





                                                        Yep, remember having the same problem. I have just removed the problematic import and restarted eclipse to make it works again.

                                                        – Tobliug
                                                        Oct 14 '16 at 13:57











                                                        1














                                                        If you are in windows os and dont need any proxy
                                                        then delete the whole proxy setting



                                                        <proxies>
                                                        <proxy>
                                                        ..................
                                                        </proxy>
                                                        </proxies>


                                                        and replace with



                                                        <proxies/> 


                                                        and then do a maven clean build






                                                        share|improve this answer



























                                                          1














                                                          If you are in windows os and dont need any proxy
                                                          then delete the whole proxy setting



                                                          <proxies>
                                                          <proxy>
                                                          ..................
                                                          </proxy>
                                                          </proxies>


                                                          and replace with



                                                          <proxies/> 


                                                          and then do a maven clean build






                                                          share|improve this answer

























                                                            1












                                                            1








                                                            1







                                                            If you are in windows os and dont need any proxy
                                                            then delete the whole proxy setting



                                                            <proxies>
                                                            <proxy>
                                                            ..................
                                                            </proxy>
                                                            </proxies>


                                                            and replace with



                                                            <proxies/> 


                                                            and then do a maven clean build






                                                            share|improve this answer













                                                            If you are in windows os and dont need any proxy
                                                            then delete the whole proxy setting



                                                            <proxies>
                                                            <proxy>
                                                            ..................
                                                            </proxy>
                                                            </proxies>


                                                            and replace with



                                                            <proxies/> 


                                                            and then do a maven clean build







                                                            share|improve this answer












                                                            share|improve this answer



                                                            share|improve this answer










                                                            answered May 10 '16 at 17:48









                                                            user3123372user3123372

                                                            454216




                                                            454216





















                                                                1














                                                                If none of the above works then try and go this question and answer:
                                                                Maven error "Failure to transfer..."



                                                                and delete your .lastUpdated files.






                                                                share|improve this answer





























                                                                  1














                                                                  If none of the above works then try and go this question and answer:
                                                                  Maven error "Failure to transfer..."



                                                                  and delete your .lastUpdated files.






                                                                  share|improve this answer



























                                                                    1












                                                                    1








                                                                    1







                                                                    If none of the above works then try and go this question and answer:
                                                                    Maven error "Failure to transfer..."



                                                                    and delete your .lastUpdated files.






                                                                    share|improve this answer















                                                                    If none of the above works then try and go this question and answer:
                                                                    Maven error "Failure to transfer..."



                                                                    and delete your .lastUpdated files.







                                                                    share|improve this answer














                                                                    share|improve this answer



                                                                    share|improve this answer








                                                                    edited May 23 '17 at 11:47









                                                                    Community

                                                                    11




                                                                    11










                                                                    answered May 25 '16 at 10:36









                                                                    iaforekiaforek

                                                                    98821534




                                                                    98821534





















                                                                        1














                                                                        1. Update Maven Project and check the option "Force update of Snapshots/Releases", it will remove errors.

                                                                        2. If not, Maven clean and install the Project.

                                                                        3. Still the error isn't removed, repeat step 1.

                                                                        It worked for me :)






                                                                        share|improve this answer



























                                                                          1














                                                                          1. Update Maven Project and check the option "Force update of Snapshots/Releases", it will remove errors.

                                                                          2. If not, Maven clean and install the Project.

                                                                          3. Still the error isn't removed, repeat step 1.

                                                                          It worked for me :)






                                                                          share|improve this answer

























                                                                            1












                                                                            1








                                                                            1







                                                                            1. Update Maven Project and check the option "Force update of Snapshots/Releases", it will remove errors.

                                                                            2. If not, Maven clean and install the Project.

                                                                            3. Still the error isn't removed, repeat step 1.

                                                                            It worked for me :)






                                                                            share|improve this answer













                                                                            1. Update Maven Project and check the option "Force update of Snapshots/Releases", it will remove errors.

                                                                            2. If not, Maven clean and install the Project.

                                                                            3. Still the error isn't removed, repeat step 1.

                                                                            It worked for me :)







                                                                            share|improve this answer












                                                                            share|improve this answer



                                                                            share|improve this answer










                                                                            answered Mar 22 '17 at 11:20









                                                                            Anand ChoukseyAnand Chouksey

                                                                            111




                                                                            111





















                                                                                1














                                                                                We have the Proxy set on company level.



                                                                                After disabling proxy in Internet Explorer this issue was solved (looks like it is then disabled on 'system' level), so all other browsers will pick this change too.



                                                                                Now I can issue MVN commands from CMD prompt and I have no problem while e.g.



                                                                                "Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-webapp/1.0/maven-archetype-webapp-1.0.pom"



                                                                                ...that was causing 'Build failure'



                                                                                Disabling proxy in IE needs to be done on daily basis in our case, because on each system start it gets set






                                                                                share|improve this answer



























                                                                                  1














                                                                                  We have the Proxy set on company level.



                                                                                  After disabling proxy in Internet Explorer this issue was solved (looks like it is then disabled on 'system' level), so all other browsers will pick this change too.



                                                                                  Now I can issue MVN commands from CMD prompt and I have no problem while e.g.



                                                                                  "Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-webapp/1.0/maven-archetype-webapp-1.0.pom"



                                                                                  ...that was causing 'Build failure'



                                                                                  Disabling proxy in IE needs to be done on daily basis in our case, because on each system start it gets set






                                                                                  share|improve this answer

























                                                                                    1












                                                                                    1








                                                                                    1







                                                                                    We have the Proxy set on company level.



                                                                                    After disabling proxy in Internet Explorer this issue was solved (looks like it is then disabled on 'system' level), so all other browsers will pick this change too.



                                                                                    Now I can issue MVN commands from CMD prompt and I have no problem while e.g.



                                                                                    "Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-webapp/1.0/maven-archetype-webapp-1.0.pom"



                                                                                    ...that was causing 'Build failure'



                                                                                    Disabling proxy in IE needs to be done on daily basis in our case, because on each system start it gets set






                                                                                    share|improve this answer













                                                                                    We have the Proxy set on company level.



                                                                                    After disabling proxy in Internet Explorer this issue was solved (looks like it is then disabled on 'system' level), so all other browsers will pick this change too.



                                                                                    Now I can issue MVN commands from CMD prompt and I have no problem while e.g.



                                                                                    "Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-webapp/1.0/maven-archetype-webapp-1.0.pom"



                                                                                    ...that was causing 'Build failure'



                                                                                    Disabling proxy in IE needs to be done on daily basis in our case, because on each system start it gets set







                                                                                    share|improve this answer












                                                                                    share|improve this answer



                                                                                    share|improve this answer










                                                                                    answered Jul 28 '17 at 10:18









                                                                                    regreg

                                                                                    3212615




                                                                                    3212615





















                                                                                        1














                                                                                        This problem was solved by following steps -



                                                                                        1. Go to the local m2 repository and find the directory
                                                                                          org/apache/maven/plugins/maven-surefire-plugin.

                                                                                        2. Delete the problematic version.

                                                                                        3. maven update the project, then download it again.





                                                                                        share|improve this answer





























                                                                                          1














                                                                                          This problem was solved by following steps -



                                                                                          1. Go to the local m2 repository and find the directory
                                                                                            org/apache/maven/plugins/maven-surefire-plugin.

                                                                                          2. Delete the problematic version.

                                                                                          3. maven update the project, then download it again.





                                                                                          share|improve this answer



























                                                                                            1












                                                                                            1








                                                                                            1







                                                                                            This problem was solved by following steps -



                                                                                            1. Go to the local m2 repository and find the directory
                                                                                              org/apache/maven/plugins/maven-surefire-plugin.

                                                                                            2. Delete the problematic version.

                                                                                            3. maven update the project, then download it again.





                                                                                            share|improve this answer















                                                                                            This problem was solved by following steps -



                                                                                            1. Go to the local m2 repository and find the directory
                                                                                              org/apache/maven/plugins/maven-surefire-plugin.

                                                                                            2. Delete the problematic version.

                                                                                            3. maven update the project, then download it again.






                                                                                            share|improve this answer














                                                                                            share|improve this answer



                                                                                            share|improve this answer








                                                                                            edited May 8 '18 at 19:49









                                                                                            Saikat

                                                                                            2,86564362




                                                                                            2,86564362










                                                                                            answered Mar 30 '17 at 9:26









                                                                                            user7790949user7790949

                                                                                            111




                                                                                            111





















                                                                                                0














                                                                                                If you are not behind any proxy and still getting connection timeout error, please check firewall settings/ antivirus. Sometimes firewall may block the connectivity from any tool (like Eclipse/STS etc..)






                                                                                                share|improve this answer



























                                                                                                  0














                                                                                                  If you are not behind any proxy and still getting connection timeout error, please check firewall settings/ antivirus. Sometimes firewall may block the connectivity from any tool (like Eclipse/STS etc..)






                                                                                                  share|improve this answer

























                                                                                                    0












                                                                                                    0








                                                                                                    0







                                                                                                    If you are not behind any proxy and still getting connection timeout error, please check firewall settings/ antivirus. Sometimes firewall may block the connectivity from any tool (like Eclipse/STS etc..)






                                                                                                    share|improve this answer













                                                                                                    If you are not behind any proxy and still getting connection timeout error, please check firewall settings/ antivirus. Sometimes firewall may block the connectivity from any tool (like Eclipse/STS etc..)







                                                                                                    share|improve this answer












                                                                                                    share|improve this answer



                                                                                                    share|improve this answer










                                                                                                    answered May 28 '17 at 7:58









                                                                                                    Shuvankar SarkarShuvankar Sarkar

                                                                                                    329310




                                                                                                    329310





















                                                                                                        -3














                                                                                                        First, You should check whether Maven tool is installed on your machine or not!!!






                                                                                                        share|improve this answer



























                                                                                                          -3














                                                                                                          First, You should check whether Maven tool is installed on your machine or not!!!






                                                                                                          share|improve this answer

























                                                                                                            -3












                                                                                                            -3








                                                                                                            -3







                                                                                                            First, You should check whether Maven tool is installed on your machine or not!!!






                                                                                                            share|improve this answer













                                                                                                            First, You should check whether Maven tool is installed on your machine or not!!!







                                                                                                            share|improve this answer












                                                                                                            share|improve this answer



                                                                                                            share|improve this answer










                                                                                                            answered Jul 13 '18 at 7:44









                                                                                                            user2964628user2964628

                                                                                                            45




                                                                                                            45















                                                                                                                protected by Mark Rotteveel Sep 23 '18 at 8:08



                                                                                                                Thank you for your interest in this question.
                                                                                                                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                                                                                Would you like to answer one of these unanswered questions instead?



                                                                                                                Popular posts from this blog

                                                                                                                Darth Vader #20

                                                                                                                How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

                                                                                                                Ondo