We have our own version of “createPlayBinaryTarDist” where we do not copy external dependency into the tar file. Instead, we create a metadata file where we put the Artifactory location of the external dependency, to be downloaded during deploy time. This generates a very thin artifact given the number of dependencies we have in our project.
Gradle renames artifacts (see link below) to maintain uniqueness when it puts it into the
lib directory. So if the artifact name is foo.jar, it renames it by prefixing the group, like com.xyz-foo.jar.
Since there is no easy way to get this renamed file name, it is hard for us to create this metadata file unless we replicate the logic on our end.
Are there any plans to expose this logic or provide with a before/after names of the external dependencies?