This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-23
Channels
- # announcements (66)
- # babashka (41)
- # beginners (93)
- # calva (10)
- # cider (2)
- # clj-kondo (112)
- # cljs-dev (6)
- # cljsrn (1)
- # clojure (44)
- # clojure-dev (10)
- # clojure-europe (35)
- # clojure-italy (15)
- # clojure-nl (3)
- # clojure-uk (2)
- # clojurescript (38)
- # conjure (1)
- # datalevin (1)
- # datomic (16)
- # deps-new (4)
- # events (7)
- # figwheel-main (1)
- # fulcro (59)
- # graalvm (21)
- # integrant (3)
- # introduce-yourself (8)
- # jobs-discuss (2)
- # malli (23)
- # membrane (11)
- # membrane-term (2)
- # missionary (17)
- # off-topic (7)
- # pathom (23)
- # pedestal (6)
- # polylith (7)
- # portal (25)
- # releases (1)
- # remote-jobs (3)
- # reveal (5)
- # shadow-cljs (43)
- # spacemacs (7)
- # sql (18)
- # tools-deps (33)
- # vim (10)
- # xtdb (36)
~/deptest/
.
├── b
│ ├── deps.edn
│ └── pom.xml
└── deps.edn{:paths ["."]
:deps {b/b {:local/root "./b"}}}I want to
clj -Stree to resolve even the deps that ./b/deps.edn has
@d.ian.b I would expect it to -- but unless you are using a very recent version of the CLI, :local/root deps can get "stale" and you need -Sforce to get them picked up.
hum nice, it got
and if I want to have the test aliases paths/devs for ./b/deps.edn?
What does clojure -version say? The most recent version is 1.10.3.1029
1.10.3.1020, upgrading now
i think i've missed to add some deps
thanks 🙂
I'm taking a look at your posts
right now I'm working for a company that uses boot-clj and I'm using macbook m1
There are a lot of issues with even how it would work to process aliases from dependencies. Lots of unanswered questions.
if it got a keyword-name-namespaceish for a project module and aliases got resolved like: clj -M:b/test
I'm not getting into it -- that's something complex for the core team to figure out.
1Nearly every simple, obvious suggestion is wrong here 🙂
hahahahhaha yeah, I was just asking why something like couldn't get to be possible
What if multiple dependencies provided the same alias?
What if you had a user-level alias and you add a dependency to a project -- which should have priority?
Right now, we have three well-defined contexts in a direct progression: project deps take precedence over user deps which take precedence over root deps.
If aliases can start to come from dependencies, there's a whole tree of places for them to start coming from...
boot doesn't work on it hahaha, I'm trying to migrate stuff to deps, trying to have a deps.edn root for every git repo in the company
Our build.clj at work reads the deps.edn from subprojects -- using tools.deps.alpha -- and merges in aliases from them and builds a "basis" for operations (such as running tests).
if it got a keyword-name-namespaceish for a project module and aliases got resolved like: clj -M:b/test
@seancorfield thanks for helping 🙂
there's a way to convert build.boot file to a deps.edn file?
some project for it?
Not that I know of.
What we did with boot was move our dependencies to deps.edn files and then add code to boot to read those files. And then we migrated to the CLI 🙂
But that was three and a half years ago I think.
hum ok, then it need some hard work 😅