This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-11
Channels
- # announcements (3)
- # asami (4)
- # babashka (79)
- # babashka-sci-dev (47)
- # beginners (97)
- # biff (12)
- # calva (7)
- # clj-commons (3)
- # clj-kondo (22)
- # clj-on-windows (13)
- # cljdoc (31)
- # cljfx (2)
- # cljs-dev (1)
- # clojure (85)
- # clojure-austin (4)
- # clojure-dev (12)
- # clojure-europe (15)
- # clojure-italy (8)
- # clojure-nl (4)
- # clojure-uk (4)
- # community-development (19)
- # conjure (3)
- # core-typed (40)
- # cursive (9)
- # datahike (21)
- # datomic (1)
- # emacs (7)
- # exercism (2)
- # graalvm (20)
- # graphql (1)
- # honeysql (16)
- # jobs (1)
- # malli (2)
- # off-topic (3)
- # pathom (28)
- # pedestal (3)
- # polylith (7)
- # reitit (14)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (4)
- # shadow-cljs (21)
- # sql (21)
- # testing (8)
- # tools-deps (23)
- # vscode (8)
- # xtdb (38)
When migrating to polylith is it avoidable to change the namespaces? I was investigating for an OS-project that is distributed mainly as a library and we never used our org as the top-ns. So when switching we would have to change our api-ns to use the org as well. I guess that is unavoidable but anyone has a better idea?
https://clojurians.slack.com/archives/C013B7MQHJQ/p1648058426674519?thread_ts=1648058426.674519&cid=C013B7MQHJQ has a thread with some discussion of using polylith for libraries
I don't think polylith is great for it, more geared towards building applications than libraries
Hey thanks, I was worried that there is a catch somewhere since it is more focused on apps. So I guess we will wait 'til this is figured out.
It could be a separate tool to package a project into another namespace when building a jar. It shouldn’t be rocket science to implement, but I don’t think it should be included in the poly tool by default, but maybe as a custom command, when that is implemented.