Ahhh, that's probably a frequent problem as well.
Thanks
Brian E Fox wrote:
There's an open issue for this, that maven should try to care about the
content of at least the metadata and not just take garbage. It
frequently happens to travelers when they hit a login page to a public
wifi.
I'm not sure if fail is the right move, nor do I think warn is correct. That
is unless some other behavior is put in place. Namely, a checksum failure in
a repository should simply continue to the next repository.
Just because one repository has a corrupt artifact doesn't mean that it
should be
This situation with OpenQA's repo etc is completely unacceptable, and
it should be embarrassing for them as well.
Does anyone know someone who works there who can help change things
for the better? I know we had similar troubles with a Maven mirror a
while back until they were removed from the
, April 30, 2008 5:18 PM
To: users@maven.apache.org
Subject: Re: default checksumPolicy is warn. Can we switch to fail ?
I'm not sure if fail is the right move, nor do I think warn is correct.
That
is unless some other behavior is put in place. Namely, a checksum
failure in
a repository should simply
