Any news on this topic? We are experiencing exactly the same situation: JARs from repo1 get corrupted (archive in archive), POMS are missing, and we also use a company proxy.
For the corrupt artifacts, our artifactory log says this: 2010-09-27 10:52:04,217 [http-8085-1] [WARN ] (o.a.e.DownloadServiceImpl:205) - Sending HTTP error code 409: Failed to read POM for 'org/apache/maven/plugins/maven-jar-plugin/2.3/maven-jar-plugin-2.3.pom': only whitespace content allowed before start tag and not \u1f (position: START_DOCUMENT seen \u1f... @1:1) .. BTW: We had been using artifactory 2.1.3 successfully for quite some time. The errors started popping up after we switched to artifactory 2.2.4 (although I don't know whether this is related or just coincidence). -- View this message in context: http://forums.jfrog.org/Artifactory-delivers-corrupt-artifacts-tp5195007p5574071.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
