Maven 3 dependency resolution fails until maven-metadata-local.xml files are deleted [maven-invoker-plugin related]?

(tho maybe this -U option is only relevant for SNAPSHOTs ...).

Yes, -U only checks for SNAPSHOTs AFAIK; that said, yes, I tried it, but to no avail. – Chas Emerick May 7 at 13:38.

I've seen similar errors caused by corrupted files in my local repository. For example, if a download failed partway through, or a file in a remote repository changed after I downloaded it. Deleting the affected directories under ~/.

M2 fixed it.

Blowing away my repository does not resolve the issue; it is repeatable from a totally clean local repo. Notes added to the main question's description, along with a link to a public project's branch that is affected. – Chas Emerick May 8 at 1:00.

This issue is resolved in aether 1.12, one rev above the aether 1.11 library that ships with Maven 3.0.3. Replacing aether 1.11 with 1.12 in one's Maven install results in expected behaviour (as noted in the bug I filed). Here's hoping Maven 3.0.4 is released with aether 1.12 ASAP.

:-).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.