On 4 March 2013 15:01, Meikel Brandmeyer (kotarak) <m...@kotka.de> wrote: > The range [1.2;1.5) means that the library was tested with 1.2 up to 1.4 and > - believing in semver - their patchlevel children. 1.5 (was at that time) > not released, yet. So compatibility couldn't be guaranteed. For me this is a > reasonable approach. Sure. It might work with 1.5. Everyone is free to place > an exclusion to help the system resolve the conflict. But you must be aware > you might run into trouble.
Better yet, you can specify a test matrix for your library. Of course there's a bit of a combinatorial problem here, which however is not solved by the version ranges: in fact to be thorough you should probably run your tests with any valid selection of versions for the dependencies -- imagine if you have ten ranges including two actually released versions each specified in your project.clj... But even overlooking that, using a baseline version and explicit tests (or, failing that, a line in the README) to document what's the minimum requirement and what has been tested seems sane to me *and* it allows us to reuse the Maven infrastructure. What's there to be gained by insisting on an improved version range handling? Also, what impact would version ranges have on repeatability of builds? Cheers, M. -- -- 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.
