This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-11
Channels
- # aws (2)
- # beginners (38)
- # boot (21)
- # boot-dev (8)
- # cider (51)
- # cljsrn (3)
- # clojars (23)
- # clojure (99)
- # clojure-austin (7)
- # clojure-brasil (1)
- # clojure-dev (8)
- # clojure-dusseldorf (1)
- # clojure-estonia (20)
- # clojure-greece (4)
- # clojure-italy (3)
- # clojure-russia (1)
- # clojure-spec (28)
- # clojure-uk (47)
- # clojurescript (47)
- # core-logic (3)
- # cursive (9)
- # data-science (1)
- # datomic (50)
- # docs (12)
- # emacs (5)
- # fulcro (60)
- # graphql (33)
- # hoplon (8)
- # jobs-discuss (1)
- # keechma (31)
- # lein-figwheel (10)
- # leiningen (4)
- # off-topic (70)
- # om (1)
- # onyx (15)
- # pedestal (5)
- # re-frame (185)
- # reagent (14)
- # remote-jobs (8)
- # ring-swagger (7)
- # rum (17)
- # shadow-cljs (193)
- # specter (6)
- # sql (51)
- # unrepl (8)
Hello everyone! Help me plz 🙂 Lein start output this for every command:
Tried to use insecure HTTP repository without TLS.
This is almost certainly a mistake; however in rare cases where it's
intentional please see `lein help faq` for details.
Our team ran into the same "insecure http without TLS problem". Leiningen 2.8.1 generates this message when we use our local http nexus server. As this just kills Leiningen rather than just being a warning, we have downgraded to 2.7.x and will stay on that version for all projects using nexus. Hopefully we will get the new https based artifactory service configured as a proxy for Clojars (currently only JCenter, Maven Central) some time in 2018. Then we will look at upgrading Leiningen.
@lain you need to use HTTPS repositories with lein 2.8.1. Do you have an internal Maven server that you're running?
Thx for all 🙂 The problem was in one package in dependencies, sad but it force me to downgrade lein version 🙂 Now everything works
Our team ran into the same "insecure http without TLS problem". Leiningen 2.8.1 generates this message when we use our local http nexus server. As this just kills Leiningen rather than just being a warning, we have downgraded to 2.7.x and will stay on that version for all projects using nexus. Hopefully we will get the new https based artifactory service configured as a proxy for Clojars (currently only JCenter, Maven Central) some time in 2018. Then we will look at upgrading Leiningen.