Hi, As the number of Clojure projects at our company has increased, we've ended up running into more and more frequent issues where lein's "pedantic" is alerting us to conflicting versions of transitive dependencies. Up until now we've been managing this by surgically updating the lists of dependencies / exclusions in each project until everything matches up, but that's kind of like a giant game of whack-a-mole and has left us vulnerable to situations where we're unwittingly running a bunch of our CI jobs against a different version of some of our dependencies than the versions that we end up including in our final builds.
I'm curious how often this has been coming up for others, and whether or not anyone has found a solution or workaround for it that they are really happy with. I've seen a couple of cool things that people have put out there, e.g.: https://github.com/achin/lein-parent https://github.com/walmartlabs/shared-deps Both of these seem to be taking an approach somewhat similar to Maven's own solution, which is the "parent pom" / project inheritance[1] approach (along with the "managedDependencies" section of a pom file). Given that, and given that lein's dependency management is already built on top of Maven, I've been wondering if it would make sense to try to bring in support for parent projects and managed dependencies as first-class constructs in leiningen. E.g.: (defproject my-parent-project "1.0.0" :description "Parent project" :managed-dependencies [[clj-time "0.10.0"] [core.async "1.0"]]) Then you could have child projects foo and bar: (defproject foo "1.0.0" :parent-project [my-parent-project "1.0.0"] :dependencies [[clj-time] [some-other-dep "2.0.0"]]) (defproject bar "1.0.0" :parent-project [my-parent-project "1.0.0"] :dependencies [[core.async] [yet-another-dep "3.0.0"]]) In this example, foo would automatically get the correct version of clj-time from the parent, but would not drag in core.async at all. Likewise, bar would get the correct version of core.async but would not drag in clj-time. When you wanted to bump to a newer version of clj-time or core.async across all of your projects, you'd just update the parent project. I'd be really curious to hear whether there are other people out there who would find this useful, or if we're just doing something wrong :) If there is some level of interest in this I'd be happy to work on PRs for it; I've already done a fair amount of exploration. In fact, I've already put together one PR against cemerick/pomegranate to add support there for Maven's "managedDependencies", which I think would be a pre-req for getting any of the rest of this into leiningen: https://github.com/cemerick/pomegranate/pull/73 If there are other folks out there who think this might be useful, I'd be grateful for any feedback or review on the above PR. Definitely still very interested to hear what other solutions people may have come up with for this, though. [1] https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance -- 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.
