In the below examples repoBase is the URL for Artifactory, snapshotPublishRepoLocation is a snapshot repo in the Artifactory deployment, and resolverRepoLocation is the virtual repository that resolves from all repositories availabe to the Artifactory deployment including snapshotPublishRepoLocation.

Setup for artifact:

version = "0.1-SNAPSHOT"

uploadArchives {
repositories.mavenDeployer {
snapshotRepository(url: "${repoBase}/${snapshotPublishRepoLocation}")
pom.artifactId = 'example'
}
}

Setup for project that has example as a dependency:

buildscript {
repositories {
mavenRepo urls: "${repoBase}/${resolverRepoLocation}"
}
dependencies

}

This project will fail to resolve example.jar. I suspect it is because the maven deployer's unique versioning which results in the expected version in the folder hierarchy, but replaces "SNAPSHOT" with a "timestamp and an incrementing counter" (thanks to Luke Daley for pointing that out) in the name of both the pom and jar artifacts. I believe this results in the resolver being unable to find either artifact.