Clojurians Log v2

@tcrawley I just tried the clojure -Srepro -Sdeps '{:deps {binaryage/dirac {:mvn/version "1.5.8"} org.clojure/clojurescript {:mvn/version "RELEASE"} clj-logging-config {:mvn/version "1.9.12"}}}' -m dirac.main again on the same machine and it works now. so this likely confirms that it was a caching issue

Re "If no repo has it, it will report that it could not find it in the first repo it tried I believe." this is correct. If there are multiple failures, tools.deps reports the first one (which repo that is is kind of arbitrary), but really that typically means it was not able to get from any repo.

this is hard to "fix" as there's no way to know which repo it was supposed to have been downloaded from. you could report all, but in some cases (multiple repos configured), you would see a flood of errors which would not actually give you any additional info.

hmm, the message could be general without mentioning a repo or print something like “tried central (…) and 2 others” this way it is quite misleading, because I spent quite some time fishing in my config files whether clojars is really configured as my secondary repo

I ended up hardcoding :mvn/repos in my deps.edn just to be sure, but I couldn’t force their order to really confirm that clojars was actually tried

these messages are just coming out of maven and are only one of many errors that could be reported (differing only in message). doing what you just suggest means basically parsing and analyzing error message strings emitted from maven

ah, nevermind, I see

if you use the mvn tool itself, I think it makes similar choices iirc