Fork me on GitHub
#leiningen
<
2017-11-27
>
norman05:11:12

I had a build machine on Java 7 that I had to update to Java 8 to use lein 2.8.1

norman05:11:13

Due to: Could not transfer artifact clojure-complete:clojure-complete:jar:0.2.4 from/to clojars (https://repo.clojars.org/): Received fatal alert: protocol_version

norman05:11:44

This is not quite the same error being reported above, but I believe it’s what alexmiller is referring to

norman06:11:25

Actually, not the SNI issue - it’s that http://repo.clojars.org requires TLS1.2 now

norman06:11:59

LEIN_JVM_OPTS=-Dhttps.protocols=TLSv1.2 will work around the protocol_version issue

norman06:11:07

I’m kind of curious why downgrading to lein 2.7.1 with Java 7 works though. I assume it’s a side effect of something around the change that requires HTTPS for all maven servers over HTTP, but I can’t quite imagine what exactly the connection there would be

Alex Miller (Clojure team)15:11:08

lein 2.8 changed the default url for clojars to the CDN url (iirc that’s https://repo.clojars.org vs the former https://clojars.org/repo

Guilhem Brouat 11:11:39

Hello ! I allow myself to repost this here, because I couldn't find any solution...

p-himik12:11:59

Is there any way to make lein repl exit on Ctrl+C?

norman14:11:23

I’d imagine SIGINT processing is backed pretty deep into the repl

marshall19:11:28

Is there a static URL for a specific version of the lein installer? I need to install 2.7.1 specifically in an automated build process

bostonaholic20:11:07

that or line #4

bostonaholic20:11:12

ah, you’re probably talking about the bash installer

marshall20:11:15

yeah that one 🙂

marshall20:11:28

unfortunately the zipped release doesn’t seem to contain the installer script

bostonaholic20:11:25

you could unzip the source from the release checkout

bostonaholic20:11:10

I would assume that is immutable

noisesmith20:11:17

also, lein upgrade 2.7.1 will ensure that you are using that version, regardless of how you get lein if you get lein in a sensible way