This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-04
Channels
- # announcements (4)
- # beginners (110)
- # boot (6)
- # calva (23)
- # cider (14)
- # cljdoc (5)
- # cljs-dev (50)
- # cljsrn (3)
- # clojure (105)
- # clojure-europe (3)
- # clojure-italy (46)
- # clojure-nl (6)
- # clojure-spec (19)
- # clojure-sweden (1)
- # clojure-uk (78)
- # clojurescript (66)
- # core-async (5)
- # cursive (19)
- # data-science (16)
- # datomic (3)
- # events (2)
- # fulcro (11)
- # hoplon (53)
- # jobs (4)
- # jobs-discuss (6)
- # keechma (51)
- # leiningen (3)
- # nrepl (25)
- # off-topic (95)
- # parinfer (8)
- # precept (1)
- # reitit (61)
- # remote-jobs (1)
- # rewrite-clj (75)
- # ring-swagger (2)
- # robots (3)
- # shadow-cljs (43)
- # tools-deps (28)
- # vim (2)
curl -O
clj -Sdeps '{:deps {org.apache.mxnet/mxnet-full_2.11-linux-x86_64-cpu #:local{:root "mxnet-full_2.11-linux-x86_64-cpu-1.4.1.jar"}}}'
Error building classpath. 1 problem was encountered while building the effective model for org.apache.mxnet:mxnet-core:[unknown-version]
[FATAL] Non-resolvable parent POM for org.apache.mxnet:mxnet-core:[unknown-version]: Could not find artifact org.apache.mxnet:mxnet-parent:pom:INTERNAL in central (You might need to add a maven repo if that parent pom isn’t in maven central
The weird thing is that this works:
clj -Sdeps '{:deps {org.apache.mxnet/mxnet-full_2.11-linux-x86_64-cpu {:mvn/version "1.4.1"}}}'
we do have a known issue that repos defined in the pom don't get used and that may be the issue here
but then the above should also not work, right?
the last example there is a different path and relies on the maven repo to resolve artifacts (https://clojure.atlassian.net/projects/TDEPS/issues/TDEPS-46 is the issue I'm thinking of)
when you load a jar dep, tools.deps is reading the model and resolving the deps
I think it's in the tools.deps pom reader where more needs to be done
I'm not sure if TDEPS-46 s whats going on here. Just let me know if you want a separate JIRA to document this failure case
you could leave a comment on that ticket so it can be checked and spun out if needed
It seems I can no longer comment: could you give permission to <mailto:[email protected]|[email protected]>
I don't think so? I think that's still a todo
yeah, that's not supported atm and I don't actually see a ticket for it, although that would be fine if you wanted to file one https://clojure.atlassian.net/servicedesk/customer/portal/1
@dm3 I've got repository mirroring working, if we're talking about the same thing. My deps.edn config includes:
:mvn/repos {"central" {:url "(I had to use http because I couldn't add a self-signed certificate to the java trust store in my particular case)
I suppose that having all that config in settings.xml breaks repeatability though, so a pure tools.deps solution would be very nice indeed.
(Er, maybe it is repeatable after it's all cached? Perhaps you could drop the settings.xml after that point and it would still download what it needed from "my-mirror." I'm not sure.)
well that's not mirroring, that's just replacing the repo
that should work
maven actually has support for mirrors (or maybe the term is different, I can't remember)
mirrors being duplicate repos that can serve the same content
Yeah I think I've seen the word "mirror" used for both meanings so I'm not sure what term to use. It is at least called "mirrors" in settings.xml (the <mirrors> section). On first request, Nexus will download and cache the needed artifacts from maven central or clojars, and then the client downloads everything from Nexus. Is that different from what you're talking about?
I think I've also heard it called "proxying"
But that's also confusing because "proxying" usually refers to using an http proxy
Maybe what I'm doing is just one species of mirroring: http://maven.apache.org/guides/mini/guide-mirror-settings.html (third bullet point)