Hi. I am using maven 2.2.1, and when I call a command: $ mvn deploy:deploy-file -Dfile=dist/test.jar -DgeneratePom=false -DpomFile=pom.xml -DgroupId=com.test -DartifactId=test -Dversion=1.0 -Dpackaging=jar -DrepositoryId=internal -Durl=dav:http://10.1.1.7/maven
I can see that the file is uploaded twice: first the byte counter goes up to the size of the jar file, stops for a sec, and then continues to go up again, and stops after twice as many bytes have been uploaded. When I run it with -X, here is what I get: [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'a0de335869312b8bc8ac43dae84fefe961aa762c'; remote = '4beb39a6b4121321c394ba4e6820b141060cd253' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'a0de335869312b8bc8ac43dae84fefe961aa762c'; remote = '4beb39a6b4121321c394ba4e6820b141060cd253' - IGNORING Then, when I compile the project that depends on test.jar, I get warnings that checksums mismatch. Also, the file is downloaded twice, retrying after first checksum mismatch, and ignoring it later. This is not a big deal for now, but I my boss said that checksum mismatch policy can be changed in maven to fail the build, and we will consider this. What am I doing wrong here? I tested it with maven 2.1.0 and this works fine. I did some research and it looks as though it is connected to the http wagon implementation change from Sun HttpConnection to commons-httpclient in maven 2.2.0. However, I also read that maven 2.2.1 reverts the default to be lightweight again (HttpConnection), but my results would suggest something different? I don't want to go back to maven 2.1.1, but I also don't want to keep two mavens, one for normal use, and one for deploys specifically. Thanks and regards. -- View this message in context: http://old.nabble.com/Invalid-checksums-when-deployoing-to-remote-repo-tp26542128p26542128.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
