tools-build

roklenarcic 2024-05-08T11:01:19.117269Z

I have a deps.edn file that has a dependency that is not in public maven repos, and the file also has `

:mvn/repos
defined with a private mvn repo with that dependency. Then I have another deps.edn file that references the first one with :local/root dependency. If I try running clj -X:deps prep in this one it fails with Could not find artifact … referring to the one artifact from the private repo. Is there any way to fix that other than declaring :mvn/repos in the second deps too?

Kirill Chernyshov 2024-05-08T11:20:40.414059Z

no "Repositories declared in dependency poms or deps.edn are not used - all necessary repositories must be defined in the top deps.edn file being used." from https://clojure.org/reference/deps_edn#procurers_mvn

roklenarcic 2024-05-08T11:21:34.169029Z

Hm, thanks

roklenarcic 2024-05-08T11:24:00.528449Z

Is it possible to declare these at a system level?

roklenarcic 2024-05-08T11:26:11.924359Z

I’ve got a deps.clj file in my .clojure folder.

Kirill Chernyshov 2024-05-08T11:29:01.031669Z

also no. maven procurers must be defined in deps.edn you use to build app. there are only two exceptions: maven central and clojars which are defined statically somewhere in the code

Kirill Chernyshov 2024-05-08T11:31:10.970609Z

maven has the same behaviour, I guess for security purposes

dpsutton 2024-05-08T13:04:59.100869Z

It’s a security thing. I think I have an http://ask.clojure.org request for the tooling to enumerate all of the :mvn/repos it finds in your dep tree to make it easy to add these if you like. Because right now you have to search for them in your tree

seancorfield 2024-05-08T15:53:47.077429Z

And just FYI this is a #tools-deps Q, not a #tools-build Q. Just making sure you are aware that there are two separate channels for those.

roklenarcic 2024-05-08T16:12:25.514059Z

Oh yeah, my apologies