Has anyone figured out a workaround for this yet? I think this should be a necessary feature for build reproducibility and for deployments.

For example, we manage deployments through gradle and deploy to multiple environments. We want to deploy the same snapshot artifact set through all QA testing environments before releasing the build. In order to do that we have to depend on a specific snapshot version.

I got into the same issue and I see this problem like a real bug, there is a reason of why this issue have not been addressed?, and repeating the question, has anyone figured out a workaround for this yet?.

You might want to try this out in Gradle 2.0 which is now released, I haven't tested if it has been fixed or not. I switched to using real versions and incrementing the version every build which aligns with Continuous Delivery since every artifact in Continuous Delivery is considered a release candidate.

Any versioning scheme not using the snapshot resolver should work though, like adding a timestamp to the artifact name <major>.<minor>.<build>-<timestamp>. If you have binary dependencies that you wish to always take the latest artifact (to mimic snapshot functionality), you can use the ivy resolve pattern for 'latest.release' or 'latest.version' in the dependency definition instead of the version number. This is bad practice though, in my opinion.

Hope that helps

I could really use a fix for this

I was just bitten by this as well. Would like to pin my app to a specific version of Spring Framework 4.2.0.BUILD-SNAPSHOT in order to avoid frequent downloads of new builds and to ensure build reproducibility. Any workaround suggestions would be appreciated.

I've opened a pull request