On Nov 11, 2009, at 10:14 AM, Joe Bohn wrote:
Thanks for documenting this Jeff. Hopefully this will be a
temporary work-around which can later be removed once things are
fixed in the repository.
Which brings me to the next point - what can be done to really fix
this? I guess Sun owns this repo? We could push to get the redirect
removed from https://maven-repository.dev.java.net/nonav/
repository/ ... but the net result would be that our builds would
still fail because we would never get the artifacts that we need
from that repo or its replacement.
Any ideas?
I believe that the fundamental "problem" is in the maven dependency
report plugin. So, fixing that would seem to be the way to truly fix
the problem. Well, I guess java.net could move the repo back to the
original location. Anyway, seems like we have an acceptable solution,
for now...
--kevan
