4 ms·
You can, but this is discouraged. Unlike in other version management systems, Clojure tools do not use lockfiles; you're expected to be explicit about the versi
by nathell 6y ago
You can, but this is discouraged. Unlike in other version management systems, Clojure tools do not use lockfiles; you're expected to be explicit about the version numbers you want.
https://nelsonmorris.net/2012/07/31/do-not-use-version-ranges-in-project-clj.html https://nelsonmorris.net/2012/07/31/do-not-use-version-range...
- regularfry 6y agoWhy no lockfiles? I'm sure there's a reason, I just don't know what it is.
- nathell 6y agoThis question merits a detailed answer that I can't provide right now, but here are some pointers: https://hypirion.com/musings/lockfiles-are-not-the-only-option https://hypirion.com/musings/lockfiles-are-not-the-only-opti... https://stackoverflow.com/questions/44521542/why-doesnt-gradle-or-maven-have-a-dependency-version-lock-file https://stackoverflow.com/questions/44521542/why-doesnt-grad...
- regularfry 6y agoAll those links really tell me is that the problem lockfiles solve has been arbitrarily ignored. "A solution can exist, it's just not currently implemented" seems to be the state of things, unless I've misread it. I'm all up for saying "thou shalt specify precise versions of library dependencies", but the specific case of `org.clojure/clojure` seems qualitatively different in that a precise version influences your consumers, and leaving it unspecified means your library might not work at all.