This message was deleted.

The idiomatic approach would be to use the maven coordinates (not the URL, which the repository/resolution would build up internally). What is the subsequent task doing?

Writing out the url to some of the artifacts to a file so another tool knows where to download it from. Not exactly the most idiomatic usage of Maven

seems sketchy. The other tool would need to be Maven-aware to get all the right stuff (incl. transitive dependencies, etc). Not aware how to get a URL for a published artifact. You could have a Gradle configuration that resolved the artifact from Maven and tasks(s) that then copy it (or otherwise process it).

It is pretty sketchy. We're basically abusing our maven repo as an S3 bucket (for unfortunate organizational reasons) and piggybacking off of the maven publish configuration we already have in our setup (so nothing transitive or anything like that). Just uploading and downloading a single file

Painful. You don’t necessarily need the published url - build it up using the same convention (group, name, version, etc).

Looks like that's my best bet forward. Thanks!