Upgraded to Artifactory 2.3.2 a while back but noticed today that I cannot seem to get new artifacts from the maven central repository proxied through artifactory. For some reason Artifactory seems to be trying to deploy the proxid downloaded artifact to my local snapshot repository instead of my local releases repository. This is the error that I see in artifactory.log.
2011-06-24 14:18:30,718 [TP-Processor29] [WARN ] (o.a.e.DownloadServiceImpl:323) - Sending HTTP error code 409: The repository 'zoot-snapshots' rejected the artifact 'zoot-sna pshots:org/springframework/ldap/spring-ldap-core-tiger/1.3.1-RELEASE/spring-ldap-core-tiger-1.3.1-RELEASE.jar' due to its snapshot/release handling policy.. I am really baffled by this as I have not modified any configuration in Artifactory or in my project pom files in months. Any idea what could be wrong here? -- View this message in context: http://forums.jfrog.org/Repository-rejected-artifact-due-to-its-snapshot-release-handling-policy-tp6513457p6513457.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
