clojure-europe 2022-02-01

we had this on sunday, and not too far off it today - spectacular, and it's going some way to atone for the awful sloppy rainy dreariness of the last few months

😎 2

😍 1

reefersleep11:02:59

Good morning 😊

😍 1

mccraigmccraig11:02:33

no gulf-stream nearby you then @U0AQ3HP9U?

reefersleep12:02:55

I can’t reach out and touch it, but I think it’d look like this every day if it weren’t for the gulf stream, so I guess it’s close enough :)

😂 3

raymcdermott12:02:13

Good morning

😍 1

raymcdermott12:02:14

Too much snow to ski today

borkdude12:02:43

@raymcdermott Where are you at?

raymcdermott14:02:02

Austria, Saalbach. One run only - snow was churned to hell

reefersleep14:02:42

Anyone know why `lein uberjar` in a new project might not produce any jars? I don’t get any error messages. I’ve fixed clashing dependencies with `:exclusions`.

borkdude14:02:31

does it just silently fail?

reefersleep14:02:51

kind of

reefersleep14:02:20

$lein uberjar
Release versions may not depend upon snapshots.
Freeze snapshots to dated versions or set the LEIN_SNAPSHOTS_IN_RELEASE environment variable to override.

reefersleep14:02:35

(these messages were also present in the project when it did produce jars)

borkdude14:02:01

it didn't for me, I had to either set that ENV variable or not depend on a snapshot

hm, ok

odd.

Lemme try

maybe you had that env variable set in your other project?

reefersleep14:02:34

Could be! Though not through my own effort, and they were created in similar ways, as I recall.

reefersleep14:02:05

It worked! Did like this: LEIN_SNAPSHOTS_IN_RELEASE=true bash -c 'lein uberjar'

borkdude14:02:31

I think you could omit the bash -c: LEIN_SNAPSHOTS_IN_RELEASE=true lein uberjar

🍻 1

reefersleep14:02:24

Guess I was wrong about the other project. It doesn’t seem to contain snapshots. Could have sworn that I saw that message while it was working, too!

reefersleep14:02:22

Yeah, that’s cleaner, thanks!

2022-02-01

Channels