Hello All,
I have a general inquiry regarding conflicting dependencies in Clojure
projects and how they affect applications at runtime. I believe this is a
common problem faced by many languages in this day and age where we try not
to reinvent the wheel by depending on the work of others. Basically: my
application depends on libraries *A*, *B*, *C*, and *D*. Libraries *B*, *C*
, *D* *also* depend on library *A*, but all of us depend on *different
versions* of library *A.* Leiningen thankfully warns us in many of these
situations by suggesting exclusions. However, how can I possibly know that
something hasn't broken? Stringent testing can give a certain degree of
confidence that things are still working, but it would seem to me that to
ensure correctness, we should include *all* versions of the dependencies
and have the functions link to their respective *versioned* identites. Does
anyone have advice on how they solve these kinds of problems on their
codebases in the wild? Thankfully nothing has broken yet (to my knowledge),
but it seems we have very few assurances here and the best we can do is
*hope* nothing is broken. Any advice is much appreciated.
Thanks,
Arthur
--
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.
