Fork me on GitHub
Jakub Holý (HolyJak)14:03:25

Hi! I have added :mvn/repos {"my-company" {:url "...."}} but I want deps to also resolve dependencies from my maven local repo. How do I add it, preferably w/o hardcoding the path of my home directory?

Alex Miller (Clojure team)14:03:25

it will already do that

Alex Miller (Clojure team)14:03:53

assuming you mean ~/.m2/repository - that's actually not a repo, but a local cache of external repos

Alex Miller (Clojure team)14:03:04

as a cache, it's checked first though so you can install stuff locally that you never deploy and it will be used

Jakub Holý (HolyJak)14:03:38

thanks, that is exactly my use case. I found out that the jar was wrongly published to the local cache.


Terminology is always as touchy topic, but would it be fair to refer as tools.deps.alpha as a package manager? If not, how would you describe the distinction? The goal for myself to group clojure tools into buckets that fit my mental model. I am happy to update my model, but I just want to see if my current understanding fits 🙂


I do not know of any precise definition of the term "package manager" that everyone would agree with, across different programming languages, but it seems to me that tools that are called by that name often do more things than tools.deps.alpha does.


This is too many words, but the page introducing tools.deps.alpha describes it thus: "a library providing a functional API for resolving dependency graphs and building classpaths that can utilize both Maven and other providers of code or artifacts"


Perhaps calling it a "dependency resolver" briefly captures the essentials?


My thoughts exactly, Andy. I agree that it would be a stretch to compare it as this would lead to further comparisons to other tools like npm