"Meikel Brandmeyer (kotarak)" <m...@kotka.de> writes: > Hi, > > Am Montag, 4. März 2013 13:00:31 UTC+1 schrieb Wolodja Wentland: >> >> It is up to a community to fix things that are broken in their toolset and >> "Do not use version ranges" is IMHO the wrong answer. >> > Huge +1.
Fixing version ranges seems like a good idea (e.g. I just ended up with commons-logging on the classpath, I think due to clojure 1.5.0 being released). Maven's answer to these issues seems to be "use dependencyManagement" [1]. I still think the valid use cases of version ranges are quite limited though. When does using version ranges make sense? Or thinking from a lein perspective, what features does lein need to provide for specifying dependency versions, and are version ranges the best way of expressing these? Hugo [1] http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-version-ranges -- -- 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.
