Or good experiences for that matter 🙂

we use this approach in #babashka https://github.com/babashka/babashka worked out fairly well I think, cc @U04V15CAJ

for me forgetting to do a submodule update was the worst of the issues 😅

I don't get it! Why do you need git submodules if you have deps.edn?

because those git submodules are projects of their own. The alternative is to use them as git deps, but this allows me to quicker iterate

It sounds I've been doing exactly what @U0B1SDL67 is asking

You can use local/root in your parent project while the git submodules are still their own independent project

> independent project > You mean like a separate repo? Oh I'm sure there's a reason but I'm wondering how this is better than having everything on the same git repo.

Yes, a separate repo. E.g.: https://github.com/babashka/sci https://github.com/babashka/fs are projects on their own but also used in babashka. I don't want to bump a git sha every time I make a small change to SCI or fs, so I use them as git submodules. Putting all those projects inside the babashka repo doesn't make sense since those projects can be independently used from babashka.

Oh, I get it now, thanks for the explanation. I was going to recommend #polylith but if you need your projects to be separate repos it wouldn't work, obviously.

That and maybe some problems can be solved using lighter weight ways

Great! This put me at ease about the idea. Thanks

I’ve looked briefly at polylith, but it seems a bit cumbersome and overkill

might be that I just haven’t quite understood it though

The way i think about it is if i have bunch of code deploying as a single purpose set of microservices, polylith seems to be a good fit. ie, one repo and multiple deployable artifacts/services. If its a single deployable artifact, use submodules and/or git/maven deps. Both approaches try to address the code resuse problem but for me it depends on what am I trying to build.

git/maven deps vs submodules comes down to your dev practices/iteration needs etc like borkdude mentioned

well in theory I could also make a small (bb) script that quickly updates the git/shas of the libraries that I'm developing

babashka is the only repo where I'm working like this. in other projects I usually switch between local/root and then back to git shas

in the babashka case, the build is also still based on leiningen which doesn't support git deps, which is why I chose git submodules initially. I needed uberjar, etc to work which wasn't there a few years ago in the deps.edn world

for development I use deps.edn there, but the deployment is done with lein

I will probably switch over in the future, but it wasn't a huge priority so far

it's occurring to me that you can switch between local/root and git shas also via an -Sdeps argument perhaps, for development

Just fyi, Clojure CLI does not work with git deps using sub modules

in bb's case that's not a problem, but good point in general

I'd like to do this as well. Ideally with different access control on submodules. Sadly I don't think cloud hosts support access control on modules