Adam Clements writes: > I'm working on a web api wrapper around a number of java/clojure libraries. > One problem that I have run into is transitive dependency conflicts, > especially when some of the projects are older than others.
If you are dealing solely with conflicts in Clojure code and not Java classes, you don't need separate classloaders; you can munge the ns forms prior to load instead: https://github.com/technomancy/metaverse This is still very experimental, but may be a promising approach with some work. -Phil -- -- 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/groups/opt_out.
