Affects Version/s: 4.7.2, 4.7.3
Fix Version/s: 4.7.4
Using virtual repository will essentially trigger a 409 error on request made for an artifact that does not exist in a given path.
Steps to reproduce (on 4.7.3):
1. Set the artifactory.repo.global.disabled in artifactory.system.properties to false.
2. Create a virtual repository and aggregate 2 repositories, one snapshot and one release (not necessary step since most instances will already include such a repo)
3. Making a request for an artifact will result in a 409, example command:
Sending response with the status '409' and the message 'The repository 'ext-snapshot-local' rejected the artifact 'ext-snapshot-local:org/grails/grails-dependencies/2.4.4/grails-dependencies-2.4.4.jar' due to its snapshot/release handling policy.'
- Important point:
Gradle build that will contain this common build script:
Will make the build fail as Gradle will 'give up' on a 409 status code instead of the previous 404 returned.