This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-27
Channels
- # announcements (4)
- # beginners (41)
- # biff (8)
- # cider (14)
- # clj-kondo (5)
- # clojure (45)
- # clojure-brasil (1)
- # clojure-europe (20)
- # clojure-nl (1)
- # clojure-norway (30)
- # clojure-uk (10)
- # clojurescript (8)
- # cursive (25)
- # datomic (20)
- # emacs (11)
- # events (1)
- # hoplon (9)
- # humbleui (7)
- # hyperfiddle (6)
- # lsp (63)
- # matrix (1)
- # observability (20)
- # off-topic (36)
- # polylith (11)
- # re-frame (2)
- # releases (1)
- # rewrite-clj (6)
- # scittle (42)
- # sql (6)
- # squint (86)
- # tools-deps (9)
is it the case that one can't refer to aliases of dependencies in ancestor deps.edn
? i.e. all dependent dependencies must be included in their :deps
for an ancestor to use them. In other words, :aliases
are only for a given library, not for anything using that library.
You can vote for this here though https://ask.clojure.org/index.php/7843/allow-specifying-aliases-coordinates-that-point-projects?show=7843#q7843
wouldn't that imply that aliases would need to be namespaced ?
oh sorry no - the aliases would be under each dependency ok
This is a thing I am interested in doing, will just need some serious thought about all the implications
@U064X3EF3 Hi Alex! The https://clojure.atlassian.net/browse/TDEPS-116 had no activity for years now and not even versioned as a “Backlog”. It would be nice to see some activity there, otherwise it looks like something abandoned or simply overlooked.
I just stumbled upon this very same old tools.deps
issue myself with a Polylith workspace recently, when I decided to factor out a few sub-projects into Polylith workspaces of their own. But, since poly has a convention to keep all dev-time dependencies under the :dev
alias, things didn’t click (quite obviously), so I had to duplicate them under the :deps
key.