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
I am trying to exclude certain artifacts from dependency:resolve, and I am
using the following configuration:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
, the simple discovery of dependent POM files is triggering this
error.
-- jim
chago wrote:
However, when i execute mvn dependency:resolve from the command line, it
still insists on attempting to download archives with a group of
com.somedomain.
Am I making a mistake?
--
View this message
