Clojurians Log v2

First off, Polylith is designed for building apps from a monorepo, not libraries. There are all sorts of issues you can run into trying to release libraries from a Polylith monorepo. Polylith can do it because because you'll only use the API (library JAR) in the context of a Polylith monorepo with the poly tool (even if it is made available via a :poly alias -- you'll be keeping versions in sync). Second, to answer your question specifically: when building a JAR for deployment, you can only have Maven dependencies in it, so any :local/root deps have to be unrolled -- "lifted" -- into the main basis, instead of being treated as (3rd party) dependencies. I designed that part (of Polylith's build) and it's taken from experiments at work and is definitely a bit sketchy. What's your specific use case for trying to publish a library here? A Polylith repo can be treated as a library via git deps -- but you still need to be very careful about any consumer that might be trying to pull in different versions of libraries from your repo.

we are building apps (external from the monorepo) and have to publish cljs lib i have understand your issues you raised, it's really something we have to work through thanks!

Yeah, that's a tricky scenario. If that is your only lib from this Polylith repo, and it's only used internally, you might get away with it. If your other projects could consume it in source form as a git dep, that would probably be the simpler solution. Otherwise, yeah, you're going to need that lifted basis approach to make a JAR with all its source components included (since whatever consumes that JAR can't use local deps into the monorepo).