Fork me on GitHub
#tools-deps
<
2021-10-11
>
seancorfield17:10:49

FYI (if you're not in the #releases channel)

pyr18:10:55

Hi! I was wondering if there was a repository that could be considered as a good example of doing multiple modules with tools.deps

pyr18:10:54

We have a lot of repositories that create multiple modules and artifacts (today with a combination of managed-dependencies, lein-sub, and lein-parent)

pyr18:10:44

I'd like to see what a similar approach would look like with tools.deps if there is good prior art

seancorfield18:10:08

@pyr You mean, like Polylith? A monorepo that has code to build various libraries and applications from various combinations of components?

seancorfield18:10:01

Maybe some of these posts will help too? https://corfield.org/tags/monorepo/

polylith 1
pyr19:10:31

@seancorfield thanks, I'll look into these

pyr19:10:14

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

borkdude19:10:49

@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).