I'm using a custom plugin that is stored in a private S3-backed ivy repository, but I'm having trouble using dynamic versions when referencing it in my gradle build script. Using a specific version works just fine with the S3-backed repository, and dynamic versions work correctly if I put the plugin in a local standard-file-based repository.
The S3 credentials that I'm using have the ability to list the contents of the bucket (tested using a separate S3 command-line tool), including the contents of the directory that gradle reports as having no versions.
This is what I'm trying to do:
And this is what it results in:
This is what is actually in the S3 repo:
If I reference one of the versions directly via classpath 'com.razerzone:library-publishing:1.0.2' then it works correctly.