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

Question

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

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

Also my networking configuration in eclipse is all set to direct and I am still unable to update the indices.

What may I have overlooked? I have searched on Google and other forums but am unable to resolve it.

Shovelnose

I had a similar problem (but behind a proxy), and I had to reload the settings.xml. I think the information that the index could not be updated is cached somehere, and after reloading the settings.xml, this cache was cleared. You have to have at least a user settings.xml XOR the reference to an installed Maven runtime (which you have configured). – Polarimeter

Answer 1

From Wojtek's link.

1. Close Eclipse
2. Delete workspace_location/.metadata/.plugins/org.maven.ide.eclipse/nexus
3. Delete workspace_location/.metadata/.plugins/org.eclipse.m2e.core/nexus
4. Go to Window->Preferences->Maven and enable checkbox named “Download repository index updates on startup”.
5. OK and restart Eclipse.

Cyathus

What if there is no "org.maven.ide.eclipse" folder? – Virulent

i don't have workspace_location/.metadata/.plugins/org.maven.ide.eclipse/nexus but it works anyway – Gaslit

@Virulent Be patient dear, patient – Ninefold

Answer 2

Just having had the same problem. Turned out the m2e plugin can't handle encrypted passwords in settings.xml. Just entered the plain password and updating the index worked again. Dependency download were not affected. They work just fine with encrypted passwords. Looks like a bug to me.

Misty

Answer 3

I have tried all these lesser deletes, but it won't help. A colleague advised to delete the whole .metadata folder. Later import projects from their place or checkout them from the svn(if you use some). This is not much more complicated, but it helped. the problem is that we don't really know, what metadata are broken, so the natural next step is to delete all of them. I think, it is the deepest possible cleaning before reinstallation of Eclipse + plugins.

Whosoever

Answer 4

I had to update Maven Plugin. It was not working. (Help menu > Eclipse Marketplace > type Maven > click magnifying glass) > Select Maven Plugin > Update

And then Go to Window->Preferences->Maven and enable checkbox named “Download repository index updates on startup”.

Approbation