This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-24
Channels
- # babashka (9)
- # beginners (17)
- # biff (1)
- # calva (3)
- # cider (29)
- # clj-kondo (31)
- # clojure (59)
- # clojure-austin (12)
- # clojure-brasil (12)
- # clojure-europe (35)
- # clojure-nl (1)
- # clojure-norway (72)
- # clojure-uk (1)
- # clojurescript (15)
- # clr (4)
- # conjure (1)
- # cursive (2)
- # datahike (2)
- # emacs (3)
- # hyperfiddle (114)
- # introduce-yourself (1)
- # kaocha (3)
- # malli (7)
- # off-topic (19)
- # pathom (2)
- # polylith (5)
- # portal (5)
- # reitit (5)
- # shadow-cljs (2)
- # slack-help (4)
- # tools-deps (42)
- # xtdb (6)
Next month we don’t have one. The one you are remembering is for Nov. Just waiting to confirm. Already have page data set up and ready to publish. Have asked if Yee Fay Lin is ok with the description I wrote that summarized what she sent me.
Have y’all used Clojure tools.build ? Any recommendation/opinion “for” or “against”?
one downside is that it will explode all jars into a temp directory. jars and linux are case sensitive. osx is not. So you can run into issues, usually around licensing
aka one jar includes a file LICENSE
and then another jar includes license/EPL.txt
or something. These can coexist in a jar and on linux but osx unifies the file LICENSE
with the directory license
and they cannot both exist.
and the best way to add the decent amount of boiler plate is neil add build
and modify as you need