tools-deps 2023-05-31 | Slack Archive

twashing05:05:29

tools.deps isn’t pulling foo/bar from custom-mvn-repo. There’s an entry for it in “~/.m2/settings.xml”. I also specified it in deps.edn.

{:deps {foo/bar {:mvn/version "0.0.1"}}
 ...
 :mvn/repos {"custom-mvn-repo" {:url ""}}}

But when trying to reference the :a alias, I still get the below error. Why isn’t tools.deps trying to reference my artifact from custom-mvn-repo?

clj -M:a
Error building classpath. Could not find artifact foo:bar:jar:0.0.1 in central ()

seancorfield05:05:02

What is the :a alias and why do you expect to change the repos that are searched for a basic dep you've specified?

Alex Miller (Clojure team)11:05:43

Can you just share the full deps.edn?

twashing11:05:09

@U04V70XH6 Thanks for the response. :a is just an alias that starts an nrepl. Sorry, that nomenclature just confuses the issue. Ultimately tools.deps doesn’t seem to search additional repos in :mvn/repos. And I’m unclear on why. https://clojure.org/reference/deps_and_cli#_maven

Alex Miller (Clojure team)11:05:04

It does search them

Alex Miller (Clojure team)11:05:22

You really need to share more explicitly what you’re doing so we can help

twashing11:05:25

@U064X3EF3 Because it’s a work repo, I technically can’t share that code. If it were OSS, I definitely would. Apologies. But I hear you. Let me try putting together a test repo ☝️:skin-tone-5:

Alex Miller (Clojure team)11:05:04

One thing you might try is generating a pom.xml with -Spom and see whether that looks right, then trying mvn dependency:tree

twashing11:05:10

Good suggestion. I get this…

clj -Spom

Error building classpath. Could not find artifact foo:bar:jar:0.0.1-ace77e745-SNAPSHOT in central ()

twashing11:05:03

… “central” is specified in a custom ~/.m2/settings.xml. That’s where I also tried to add my “custom-mvn-repo” (https://custom.maven.archive2/groups/public/).

twashing11:05:06

The only thing I can think of is to try with a simplified repo. More soon!

Alex Miller (Clojure team)12:05:46

The error messages can be misleading here - if an an artifact is not found in any repo, only the first error is reported, which is typically central, but that doesn’t mean your other ones weren’t searched

Alex Miller (Clojure team)12:05:39

But I notice this is a snapshot - are you sure the repo you’re adding is a snapshot repo?

Alex Miller (Clojure team)12:05:28

Depending what kind of repo this is, you might also be able to look in that url at the desired path to verify it actually exists there

twashing12:05:22

“but that doesn’t mean your other ones weren’t searched” Ah ha! “you might also be able to look in that url at the desired path to verify it actually exists there” Spot on… It turns out that my Or g is migrating to a new Maven repository. So I need to update my settings.xml, and possibly a registration. So just going through that right now. Really appreciate the feedback 👏:skin-tone-5:

2023-05-31

Channels