This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-16
Channels
- # announcements (19)
- # babashka (13)
- # beginners (7)
- # calva (8)
- # cider (25)
- # clj-kondo (12)
- # cljsrn (7)
- # clojure (60)
- # clojure-australia (5)
- # clojure-europe (59)
- # clojure-france (14)
- # clojure-gamedev (2)
- # clojure-nl (1)
- # clojure-uk (7)
- # clojurescript (43)
- # community-development (8)
- # core-async (2)
- # cursive (15)
- # datomic (75)
- # deps-new (31)
- # depstar (1)
- # fulcro (6)
- # graalvm (53)
- # holy-lambda (1)
- # juxt (3)
- # jvm (13)
- # kaocha (8)
- # lsp (109)
- # malli (14)
- # off-topic (62)
- # pathom (11)
- # pedestal (12)
- # polylith (12)
- # releases (5)
- # sci (5)
- # shadow-cljs (15)
- # sql (16)
- # tools-deps (27)
- # vim (1)
- # xtdb (14)
I want to make sure I'm understanding this (can't scroll up far enough to see where this was previously spoken about), bricks (components and bases), should not depend on other bricks directly, but can depend on libraries. Projects are used to pull different bricks together...
This approach allows you to swap out components with the same interface in projects, if a base depends on a component directly, you can't swap out the component via the project
Yes, that鈥檚 correct @allandaviesza.
depstar has been archived, after a final release (2.1.303) to fix an argument parsing bug I introduced back in 2.1.245. I'll try to carve out some time this week to get a PR up that switches the building part of poly over build-clj (my high-level wrapper around tools.build). [edited: I thought create project added depstar into new projects but I see now it does not -- which makes sense: users can build projects however they want!]
Huh. So poly cli can build project?
poly create project ... creates a project folder that has no specific "build" machinery but the poly README has an example of augmenting the generated deps.edn there to add depstar, which I want to change to talk about adding a minimal build.clj and :build alias instead, so you'd use clojure -T:build uberjar instead of clojure -X:uberjar.
But the "building part" I'm talking about above is how the poly tool itself is built into an uberjar, which currently uses depstar.
Ohh. Thank you! Understood
Hmm, that may end up being several PRs because there are several relatively unrelated uses of depstar throughout the Polylith repo. I'd mostly like to get the README updated and any examples. The actual building of poly can switch later.
I agree that tools.buildis the right way to go, both internally when we build poly.jar and in the examples in the readme. It would be really great if you could help out with that @U04V70XH6. Then I could include it in the next planned release. I haven鈥檛 checked this with @U2BDZ9JG3 yet, but I think he would prefer to switch to tools.build too.