Using the default Wagon provider or turning on preemptive authentication fixes the checksum error so Artifactory no longer returns the 409 error.
Enabling "Trust server generated checksums" for the target repository did not suppress the 409 error. I don't know if this is a bug or the intended behavior. Steven smy wrote: > > md5.my-addr.com returns cfd53d8b655b26db396dbc2515ffc321. This matches the > Artifactory computed checksum. > > There is a problem reported for Maven Wagon. See > http://jira.codehaus.org/browse/WAGON-277. Since this was not a problem > for us in 2.1.3, we haven't tried customizing the Wagon configuration. We > just use -Dmaven.wagon.provider.http=httpclient. Does anyone know the > http://maven.apache.org/guides/mini/guide-http-settings.html > httpConfiguration we should use for Artifactory? > > Steven > > -- View this message in context: http://old.nabble.com/Maven-build-fails-because-of-Artifactory-2.2.2-error-code-409-tp28057184p28075242.html Sent from the Artifactory-Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
