This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-22
Channels
- # aatree (2)
- # beginners (14)
- # boot (190)
- # cider (16)
- # cljs-dev (15)
- # cljsjs (6)
- # cljsrn (7)
- # clojure (101)
- # clojure-austin (26)
- # clojure-berlin (2)
- # clojure-estonia (4)
- # clojure-greece (53)
- # clojure-russia (46)
- # clojurescript (44)
- # core-async (12)
- # cursive (57)
- # data-science (49)
- # datomic (5)
- # emacs (8)
- # hoplon (92)
- # ldnclj (20)
- # lein-figwheel (22)
- # leiningen (4)
- # mount (37)
- # om (103)
- # onyx (26)
- # parinfer (70)
- # proton (6)
- # re-frame (32)
- # reagent (1)
- # yada (24)
I've just filed this issue with leiningen: https://github.com/technomancy/leiningen/issues/2098 I believe it's a bug, but I'm not 100% sure (as I find profiles quite mysterious) - I'm wondering if anyone here might be able to check it over, to see what they think.
@rickmoynihan: Yeah, that's a bit counterintuitive, but "correct" according to the technical spec. I guess the most sensible thing is to make the :repositories
key whitelisted, so the dependencies will be fetched.
@hypirion: No worries... it's pretty frustrating - because it means the only option that works is to have :repositories
in project.clj
but if some people/environments use gpg and others use env vars etc... then it becomes problematic having just one :repositories spec.
By correct I'm curious what you mean? Where is this behaviour specified?