From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I.e. the version catalog is stored in artifactregistry. The com.google.cloud.artifactregistry.gradle-plugin is required to resolve that dependency.

Define the repository in `pluginManagement` block, then apply it in the `plugins` block.
Settings plugins are applied bfore the `dependencyResolutionManagement` block is executed. `dependencyResolutionManagement` is not special it is evaluated during normal settings script evaluation phase.

It is already defined and applied. I can for instance pull plugins from artifactregstry from within pluginManagement. It only fails in dependencyResolutionMangement.

(I.e. it fails with Not a supported repository protocol 'artifactregistry': valid protocols are [http, https, file, gcs, s3, sftp]) which seems to imply the plugin is indeed not applied properly. :man-shrugging:

From a quick look at the sources of that plugin, only repositories in `pluginManagement` are supported.

And they also have a feature request for it: <https://github.com/GoogleCloudPlatform/artifact-registry-maven-tools/issues/71>

Thank you for the info. I though I was just configuring it wrong somehow.