This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-03
Channels
- # announcements (3)
- # beginners (114)
- # calva (42)
- # cider (90)
- # clj-kondo (3)
- # cljsrn (6)
- # clojure (40)
- # clojure-conj (4)
- # clojure-dev (3)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-quebec (1)
- # clojure-spec (3)
- # clojure-uk (130)
- # clojurescript (31)
- # cursive (3)
- # data-science (3)
- # datavis (1)
- # datomic (5)
- # dirac (3)
- # fulcro (16)
- # jobs (1)
- # joker (6)
- # music (5)
- # off-topic (14)
- # re-frame (19)
- # remote-jobs (8)
- # shadow-cljs (37)
- # slack-help (4)
- # tools-deps (22)
- # xtdb (8)
there's really two stages in clj and the first one (cp computation) should be pretty amenable to it
it makes the install story (which is already complicated) much more complicated
and in most cases the result of cp computation is a) IO-bound and b) cached and skipped
given all that, exploring this is not a high priority for me
Hi! I think I asked a while back about using self-signed certs for accessing a self-hosted maven repo over https with tools.deps. (The Leiningen equivalent is adding the path to the cert in :certificates []
.) IIRC, at the time that I asked, this was not supported with tools.deps. I can't seem to find anything about this by googling or looking on JIRA. Could anyone give me an update on whether this works these days, or point me in the right direction for how to handle this scenario?
Relevant config in deps.edn:
:mvn/repos {"central" {:url "https://<my-nexus-server>/repository/maven-public/"}}
Everything works fine over http with tools.deps, and even with https with lein
. But with https on tools.deps I get "unable to find valid certification path to requested target."Nothing has been added in this area
Could add it to Java’s certs?
That's a good solution on most OSs, but I'm on NixOS which aims to be "immutable" so the keystore is read-only. I should probably look into adding the ability to add certs to the java keystore declaratively in NixOS. Anyway, thanks for the update!
I'm struggling to import a library that I've forked on my own repo details: https://ask.clojure.org/index.php/8507/failure-on-github-import-via-deps
@sfyire I'm pretty sure that implies that the repo in question does not have a deps.edn (which it doesn't). To my knowledge, if you want to use :git/url
, the target must have a deps.edn.
@alex.joseph.whitt ah thank you
You can tell it to do that
@alexmiller how would I do that?
If you add :deps/manifest :deps
to the coord that overrides the autodetection (although you won’t get the deps in project.clj)
You could add those to the caller though if you don’t have access to modify the project
If you’ve forked it, then I’d just add a deps.edn
yeah, that's cool to know though
thank you