This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-28
Channels
- # announcements (2)
- # babashka (16)
- # bangalore-clj (1)
- # beginners (93)
- # boot (11)
- # calva (5)
- # cider (13)
- # clj-kondo (49)
- # cljdoc (14)
- # cljs-dev (1)
- # clojure (99)
- # clojure-dev (3)
- # clojure-europe (1)
- # clojure-india (1)
- # clojure-italy (9)
- # clojure-nl (3)
- # clojure-poland (1)
- # clojure-russia (1)
- # clojure-spec (31)
- # clojure-uk (21)
- # clojured (2)
- # clojurescript (18)
- # core-async (12)
- # cursive (36)
- # data-science (1)
- # datomic (54)
- # duct (3)
- # emacs (33)
- # events (1)
- # fulcro (17)
- # jobs (1)
- # joker (8)
- # keechma (1)
- # leiningen (7)
- # malli (8)
- # nrepl (19)
- # pathom (6)
- # planck (18)
- # re-frame (20)
- # reagent (18)
- # shadow-cljs (3)
- # sql (7)
- # vim (31)
hey guys , how do I get the latest version of a dependency . Do I replace the version number with "LATEST" for a particular dependency in project.clj?
I believe that should do it, but I haven't tried it myself. If the dependency you do that for is not one of your own, it seems to be asking for unpredictable changes in your code at times you cannot easily predict.
There is the lain-ancient
plugin that you can run to report which dependencies have newer versions available -- perhaps you already know of that.
Yep , I tried lein-ancient
the dependency doesn't even show up in the list of outdated dependencies and I know definitely that I am on an older version . The dependency is hosted on s3 and I am using s3-wagon 1.3.1
. I am able to switch to the latest version of the dependency if I specify the version number explicitly.
I have not used lein-ancient with anything other than dependencies on Maven Central and http://clojars.org, so haven't seen the behavior you describe. Perhaps a known limitation and/or bug in lein-ancient.