This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-13
Channels
- # beginners (71)
- # boot (61)
- # clara (49)
- # cljs-dev (9)
- # cljsjs (2)
- # cljsrn (5)
- # clojure (55)
- # clojure-android (1)
- # clojure-italy (4)
- # clojure-spec (39)
- # clojure-uk (56)
- # clojurescript (69)
- # cursive (5)
- # data-science (1)
- # defnpodcast (6)
- # devcards (1)
- # duct (12)
- # figwheel (3)
- # fulcro (18)
- # leiningen (35)
- # lumo (19)
- # midje (1)
- # off-topic (22)
- # om (3)
- # onyx (23)
- # portkey (3)
- # re-frame (20)
- # reagent (23)
- # ring-swagger (6)
- # shadow-cljs (119)
- # specter (7)
- # unrepl (25)
stuck with an odd issue I have never seen before:
chrisn@chrisn-dt:~/dev/http-kit$ lein install
Could not transfer artifact com.amazonaws:aws-java-sdk-s3:pom:1.9.0 from/to central ( ): Host name '' does not match the certificate subject provided by the peer (CN=, O="Sonatype, Inc", L=Fulton, ST=MD, C=US)
This could be due to a typo in :dependencies or network issues.
If you are behind a proxy, try setting the 'http_proxy' environment variable.
I have the same issue today as @chrisn.
Could not transfer artifact com.firebase:firebase-client-jvm:pom:2.5.2 from/to central ( ): Host name '' does not match the certificate subject provided by the peer (CN=, O="Sonatype, Inc", L=Fulton, ST=MD, C=US)
. Never seen this beforeI'm also getting a bunch of SSL certificate issues that I've never encountered before
@chrisn @podviaznikov any luck with this?
no, I also tried different version of lein(2.5 and latest one). But from reading error it seems that Maven central certs are not correct
I have a coworker experiencing this exact problem atm
I reproduced this on two arch linux machines and a windows 10 machine. I agree with @podviaznikov
@konradt95 @chrisn @podviaznikov @cjsauer https://issues.sonatype.org/browse/MVNCENTRAL-2870
nice, seems to be fixed too
@bostonaholic It's working for me now. Sweet.
Hey all, I'm trying to install leiningen on windows 7. I ran self install, added everything to my PATH, but still whenever I run lein anything it returns this: "Could not find or load main class clojure.main" has anyone encountered this before? I can't seem to find any solution online.
@derpocious stacktrace?
Where can I find the stack trace?
I'm working on doing a build in an internal, locked down environment. No access to Clojars or Maven Central. On a lein install
I'm seeing a 30 minute timeout, then lot of these exceptions:
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.clojure:clojure:pom:1.8.0 from/to central ( ): Connect to [] failed: Connection timed out (Connection timed out)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:538)
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:216)
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:193)
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom (DefaultArtifactDescriptorReader.java:281)
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor (DefaultArtifactDescriptorReader.java:186)
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process (DefaultDependencyCollector.java:412)
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process (DefaultDependencyCollector.java:544)
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies (DefaultDependencyCollector.java:240)
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:333)
sun.reflect.NativeMethodAccessorImpl.invoke0 (:-2)
sun.reflect.NativeMethodAccessorImpl.invoke (:-1)
sun.reflect.DelegatingMethodAccessorImpl.invoke (:-1)
java.lang.reflect.Method.invoke (:-1)
clojure.lang.Reflector.invokeMatchingMethod (Reflector.java:93)
clojure.lang.Reflector.invokeInstanceMethod (Reflector.java:28)
Outside of lein install
things are working well, because we are using a mirror; from profiles.clj:
:mirrors
{#"clojars|central"
{:name "internal-nexus"
:url " "}}
It seems like the lein install
task is ignoring the :mirrors. Any advice on how to get it to work from our internal Nexus instead?@hlship might be related to https://clojurians.slack.com/archives/C0AB48493/p1510600841000191 ?
Probably not; our internal build system explicitly locks down everything outside, including Clojars and Central. Our internal Nexus white-lists artifacts from there. What's odd here is that before the install, we've done a build and test, so everything needed by our project, and by Leiningen, has already been downloaded through the internal Nexus. But something about POM generation seems to be taking a different path, and is accessing directly.
But, ok, I see your point, my mirros rule may not be sufficient. I can try adding a bit more to it so ensure it matches anything .http://maven.org for example.
Dunno, just spitballing, it's the only recent change I can see that would cause this. I'm assuming that this used to work?
Well, we're sticking with 2.7.1 for the meantime. "used to work" isn't meaningful ... we're moving from a vanilla Jenkins to this internal CI based on Jenkins that operates in a significantly locked down environment. Very enterprisey.
Oh, so this isn't something that just broke today?
@hlship looks like its trying to connect to
, is that correct?
I tried adding a more specific mirror rule, but Leiningen noticed that its duplicate:
+ lein install
Leiningen's classpath: :/usr/share/java/leiningen-2.7.1-standalone.jar
java.lang.IllegalArgumentException: Multiple mirrors configured to match repository {"central" " "}: {" " {:name "internal-nexus", :url " "}, #"clojars|central" {:name "internal-nexus", :url " "}}
So I've circled back to "aether pom generation doesn't honor the :mirrors" as a working theory.
I think my issue is this: https://github.com/technomancy/leiningen/issues/2239