This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-24
Channels
- # aleph (3)
- # beginners (17)
- # boot (8)
- # cider (61)
- # cljdoc (13)
- # cljs-dev (2)
- # clojure (66)
- # clojure-boston (1)
- # clojure-italy (4)
- # clojure-nl (7)
- # clojure-russia (7)
- # clojure-spec (19)
- # clojure-uk (80)
- # clojurescript (73)
- # core-async (4)
- # cursive (6)
- # data-science (1)
- # datomic (33)
- # docs (13)
- # emacs (17)
- # figwheel-main (28)
- # fulcro (12)
- # graphql (1)
- # jobs (3)
- # leiningen (4)
- # luminus (1)
- # off-topic (1)
- # parinfer (1)
- # pedestal (46)
- # protorepl (3)
- # re-frame (30)
- # reagent (47)
- # reitit (10)
- # ring (1)
- # shadow-cljs (94)
- # spacemacs (12)
- # specter (16)
- # tools-deps (6)
- # uncomplicate (1)
- # vim (9)
Sorry folks, will need to find some time to fix that
Or revert the change, I don't know how many folks use the pom parent feature
Would it suffice to expand (sequential? type)
to (and (sequential? type) (= 1 (count type)))
since that would un-break all the [str]
common use versions out there, while letting the [sym ver path]
style destructuring thru?
Yep I wanted to actually fix that exactly that way ;)
There are also test files there if I remember correctly
I look forward to Boot 2.8.2 🙂
Hi all, tried upgrading boot today to 2.8.1 to go along with the new s3-private-wagon (1.3.2), and I can't seem to figure out how to get the credentials to load. I keep getting Secret key cannot be null
errors when attempting to connect to the private s3 repo. The credential provider is finding the s3 passphrase, and I can see the passphrase in the repository entry when I do (:repositories (get-env))
from the repl. I'm using a pretty minimal test build. Has anyone managed to get 2.8.1 working with s3-private-wagon?
@zalky Wasn't there a breaking change to how SSL/TLS is handled in 2.8.x?