You can use "lein deps :tree" to detect what different libraries depend on. Specifying an explicit Clojure dependency in your own project should override anything used by downstream dependencies. "lein ancient" is also useful in finding out of date dependencies.
I am not aware of any binary incompatibilities from using 1.5.1 AOT compiled code in Clojure 1.6 (we did provide shims and do a bit of testing to fix issues in this area). Binary compatibility across releases is not guaranteed, but it is something we strive to maintain if possible. One area where things do differ is in the hasheq functions used in hash maps and sets (which affects the sequence order for those - that order is not defined and it will change from 1.5.1 to 1.6.0). There were some potential issues around "case", which changed in implementation in 1.6, but that was reported and fixed before the final release and I tested with 1.5.1 AOT compiled classes to verify. On Tuesday, June 3, 2014 5:36:01 AM UTC-5, Mike Fikes wrote: > > I'm making use of core.async, which specifies 1.6. > > Does leiningen help with ensuring any libraries I'm using are also > compatible with 1.6? > > I'm concerned that I may have another dependency (perhaps transitive) that > is incompatible, perhaps simply by being AOT compiled with 1.5.1. > -- 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.
