I've been happy using a monorepo with boot, and a build.boot with many building blocks that can be mixed and matched for many deployables (uberjars in my case).
In my build.boot I define my internal blocks, but also defs for external deps like eg postgres and grpc. That way I have one place for these groups of dependencies to manage, and can merge them into many of my own building blocks in a flexible and consistent way. There are no checkouts, multiple outputs and consistent usage of dependencies. If I need different release management/deployment process for different deployables of my own I tend to use different release branches by deployable that my ci/CD setup triggers from. Hope that helps! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
