Classic error: unable to update index for central | http://repo1.maven.org/maven2

I came across a situation where my eclipse indigo "Unable to update index for central|http://repo1.maven.org/maven2" .

I am using an external installation of Maven 3.0.3 and m2eclipse configured with Eclipse Indigo and I am definitely not behind a proxy server.

Also, my network setup in eclipse is set to direct, and I still cannot update the indexes.

What can i miss? I searched on Google and other forums, but could not solve it.

+24
java eclipse maven m2eclipse eclipse-indigo
Aug 15 '11 at 13:26
source share
5 answers

From the Wojtek link.

  • Close eclipse
  • Delete workspace_location / .metadata / .plugins / org.maven.ide.eclipse / nexus
  • Delete workspace_location / .metadata / .plugins / org.eclipse.m2e.core / nexus
  • Go to Window-> Preferences-> Maven and check the box "Download repository index updates at startup."
  • OK and restart Eclipse.
+35
Aug 02 2018-12-12T00:
source

Just the same problem. A disabled m2e plugin cannot handle encrypted passwords in settings.xml . Just entered a simple password and updated the index, which worked again. Dependency loading was not affected. They work great with encrypted passwords. Looks like a mistake.

+1
Aug 01 '13 at
source

I tried all of these smaller deletions, but that will not help. One colleague suggested deleting the entire .metadata folder. Later import projects from their place or check them with svn (if you use them). It is not much more complicated, but it helped. the problem is that we really don’t know which metadata is broken, so the next next step is to delete all of them. I think this is the deepest cleanup before reinstalling the Eclipse + plugins.

0
Nov 13
source

I had to update the Maven plugin. He did not work. (Help menu> Eclipse Marketplace> enter Maven> click the magnifying glass)> Select Maven Plugin> Update

And then go to Window-> Preferences-> Maven and check the box "Download repository index updates at startup."

0
Jul 25 '15 at 15:03
source

If after you said you had a problem again, you can delete the .m2 folder from my documents or / home and let the IDE reload the folder for you, it solved the same problem.

-one
Jun 12 '16 at 15:45
source



All Articles