Hi. I'm sure I'm using 2.2.1. $ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_17 Java home: c:\apps\Java\java\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Also, for now to avoid the problems, I deployed all jars with maven 2.1.0, but build with maven 2.2.1, and the checksum problems you mention do _not_ occur when dependencies are downloaded, i.e. the checksums are correct. As far as I know (from reading on the web), the regression with invalid checksums was introduced in maven 2.2.0, so I think deployment with 2.1.0 and downloading with 2.2.1 should work fine? Thanks and regards. BRIAN FOX-5 wrote: > > It was fixed in 2.2.x, 2.1.x has the problems you describe. Are you > positive you're running the version you think? > > Also note that anything deployed with 2.1.x will have invalid > checksums reported even if you later use 2.2.x. They will stay that > way until redeployed or the checksums recalculated. > > On Fri, Nov 27, 2009 at 8:00 AM, wujek.srujek <[email protected]> > wrote: >> >> 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] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://old.nabble.com/Invalid-checksums-when-deployoing-to-remote-repo-tp26542128p26543893.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]
