This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-16
Channels
- # 100-days-of-code (1)
- # announcements (1)
- # beginners (93)
- # boot (46)
- # cider (40)
- # cljdoc (4)
- # cljs-dev (7)
- # clojure (78)
- # clojure-conj (12)
- # clojure-dev (17)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-spec (34)
- # clojure-uk (36)
- # clojurescript (56)
- # code-reviews (6)
- # core-async (31)
- # cursive (12)
- # datascript (9)
- # datomic (19)
- # devops (2)
- # editors (3)
- # emacs (6)
- # events (2)
- # figwheel (1)
- # figwheel-main (11)
- # fulcro (59)
- # graphql (10)
- # hyperfiddle (3)
- # keechma (5)
- # leiningen (26)
- # luminus (1)
- # nrepl (5)
- # re-frame (5)
- # reitit (10)
- # shadow-cljs (64)
- # spacemacs (29)
- # tools-deps (6)
- # uncomplicate (8)
- # vim (2)
- # yada (4)
@alexmiller Why is Clojure master SNAPSHOT lagging behind the released versions? clojure-1.10.0-master-20181001.225148-6.jar -- This makes it pretty much impossible to do multi-version testing against master as well as a recent version alpha/beta version of Clojure since the master snapshot is several versions behind.
I just started using ex-cause
in my code on 1.10.0-RC1 and now it throws compiler errors on master snapshot since that predates the addition of ex-cause
😞
the Clojure build is set up to check hourly and build if changed
but release versions are included in that so when there’s a commit, then a release before the next top of the hour, no snapshot build is ever triggered
I poked it to build now
and also added something to build nightly regardless
we’ll see how that goes
Thanks. I think this is the second time my build's blown up because of that 😞 I was surprised it was so far behind this time.
Perhaps not trying to cut a release until after a snapshot build has run might also be good practice? 🙂
(at least with this change the master snapshot should only ever get a few hours behind on the day a release is cut -- which will definitely help)
Not easily
Much appreciated @alexmiller! We're back in business testing against master! 🙂
I blew away ~/.m2/repository/org/clojure/clojure
so it's interesting to see what versions get pulled down by libraries we use (the 1.10 builds are omitted):
Retrieving clojure-1.6.0.pom from (8k)
Retrieving clojure-1.3.0.pom from (5k)
Retrieving clojure-1.7.0.pom from (8k)
Retrieving clojure-1.5.1.pom from (6k)
Retrieving clojure-1.8.0.pom from (8k)
Retrieving clojure-1.4.0.pom from (5k)
Retrieving clojure-1.2.1.pom from (1k)
Retrieving clojure-1.2.0.pom from (1k)
Retrieving clojure-1.3.0-beta1.pom from (5k)
👀Clojure 1.4.0 on clojars?
Yep, there they are, published by technomancy. Huh.