Cracked it! We took a packet trace of maven downloading the dependencies and found that an HTTP GET for the sha1 checksum in the middle of the stream for the jar..
I turned off our anti-virus software and it fixed it! It turns out that it has some sort of http scanning capability, which was doing something to the jars and sha1 files. Still doesn't add up as to why it didn't fail when nexus wasn't involved, but I can only think that it because downloading from nexus has less latency involved. Thanks for all your help! David -- View this message in context: http://www.nabble.com/Jar-Contents-getting-mixed-up%21-tp25026781p25060790.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]
