This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-11
Channels
- # announcements (4)
- # babashka (50)
- # beginners (45)
- # cider (12)
- # clara (1)
- # clj-commons (6)
- # clj-kondo (3)
- # cljdoc (3)
- # cljs-dev (44)
- # clojure (19)
- # clojure-europe (15)
- # clojure-france (1)
- # clojure-nl (13)
- # clojure-portugal (4)
- # clojure-uk (6)
- # clojurescript (3)
- # conjure (3)
- # cryogen (10)
- # datomic (23)
- # emacs (9)
- # fulcro (12)
- # graalvm (1)
- # graphql (2)
- # introduce-yourself (2)
- # jobs (4)
- # jobs-discuss (9)
- # lsp (2)
- # pathom (3)
- # polylith (23)
- # portal (1)
- # reagent (14)
- # releases (4)
- # remote-jobs (3)
- # shadow-cljs (1)
- # sql (8)
- # tools-build (7)
- # tools-deps (10)
- # xtdb (7)
FYI (if you're not in the #releases channel)
Hi! I was wondering if there was a repository that could be considered as a good example of doing multiple modules with tools.deps
We have a lot of repositories that create multiple modules and artifacts (today with a combination of managed-dependencies, lein-sub, and lein-parent)
I'd like to see what a similar approach would look like with tools.deps if there is good prior art
@pyr You mean, like Polylith? A monorepo that has code to build various libraries and applications from various combinations of components?
@seancorfield thanks, I'll look into these
we're a bit weird in the sense that we don't have a large monorepo, rather a handful of large repositories which build multiple modules
@pyr Note that you can also have multiple deps.edn projects within one git repo. We're doing that here:
https://github.com/clj-easy/graal-config
It's supported by :deps/root
. You can consume the same repo with different roots within one deps.edn file.
We don't produce any artifacts because it's not necessary (given that you're using deps.edn).