Just to be a little more clear, it appears that when Artifactory downloads an artifact from maven central repository Artifactory attempts to deploy the downloaded artifact to my local snapshot repository instead of to my remote repository cache "repo1-cache". Because my local snapshot repository is configured to only accept snapshot artifacts it rejects the attempt to deploy the artifact downloaded from maven central. My question is, why would Artifactory be trying to put artifacts that it downloads from maven central in my local snapshot repo instead of in "repo1-cache"?
-- View this message in context: http://forums.jfrog.org/Repository-rejected-artifact-due-to-its-snapshot-release-handling-policy-tp6513457p6513651.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
