This message was deleted.

I do not think that's feasible since most dependencies would be resolved from Gradle's m2 cache. (

~/.gradle/caches/modules-2/files-2.1/

) . The files downloaded to here may not include the source (unless that;s specified in the meta-data files like pom / module.json ). If a dep does not exist in your local cache and want to see where it is downloaded from, you can see that in the

network

tab of a gradle build scan that shows the URL.

I'm pretty certain that for artifacts in the cache Gradle also stores where they were originally resolved from...

since it's stored in the pom file, you should be able to see it in a build scan?

It has nothing to do with the POM, especially as the POM has no idea where it was downloaded from and there are also other possibilities like Ivy repositories or artifact only repositories. But yeah, Gradle of course knows exactly where your dependencies come from, whether they are served from the cache or not. But I don't remember any local task that could display it. Just the build scan that was already mentioned.

Are there any pointers to how the build scan plugins determines this information?

Unfortunately, the Gradle enterprise plugin that determines this information is closed source