The thing is: the CL world currently lacks a comparable mechanism. We work with CL and CLJ, and we spend much more time getting builds done in CL, because we need several tools, and integration into Jenkins is also more difficult and tiresome. This is no argument against the CL language qualities, but about tooling.

I am also not aware of repository managers for CL. Several of our libs have to be managed manually. Our CLJ libs however we can simply store in our private repo proxy. For other devs it is nothing more than a dependency they add in Leiningen and be done with it. It is trivial to set this up in Jenkins, which automatically uploads relevant artifacts into the repo. This is a fantastic and productive environment, Bundled with greater productivity in Clojure I would start new projects today pretty much always with Clojure, not CL anymore. Though CL is still interesting to study for newcomers to Lisps.