Welcome! Please see the About page for a little more info on how this works.

+1 vote
in tools.deps.alpha by

Google's Artifact Registry can be used as a Maven repository (see https://cloud.google.com/artifact-registry/docs/java/quickstart) but deps.edn cannot currently refer to this as it does not provide hooks for custom wagons/transports.

In tools.deps, there are a couple ways this could be done. First, there is an existing Maven wagon for accessing artifact registry, so adding that + the wagon transporter (we use the newer transporter framework) + registration would allow custom urls to work with the existing code.

Or, another option would be to write a custom deps procurer that talks directly to Artifact Registry, not sure of the effort there but can't possibly be too much. Probably some subset of what the code at https://github.com/GoogleCloudPlatform/artifact-registry-maven-tools is doing. Probably the hardest part is figuring out the transfer of credentials. One of the benefits of this would probably be a smaller set of external deps.

And finally, clj would need a way to provide custom procurer support, which we have not yet designed.

1 Answer

+1 vote
by
by
edited by
Is there anyway to vote for this on Jira, or should I just vote for it here?

We are using Datomic Cloud so using Leiningen is not an option, but we also have to pull in some private artifacts from Artifact Registry.

Edit: we do have access to git repo for the libs, so that should be a workable solution for us right now
by
This is the best place to vote for it. Given that few people have asked for this, I think it's unlikely to be something I would write, and maybe unlikely even to be something we would include "in the box" (although I would want to know a lot more about the dependency reqs before making such a decision).
by
Thank you Alex. I made a edit to my comment before seeing your response:

Edit: we do have access to git repo for the libs, so that should be a workable solution for us right now
...