This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-10
Channels
- # 100-days-of-code (2)
- # announcements (2)
- # aws (11)
- # beginners (114)
- # boot (6)
- # calva (11)
- # cider (11)
- # cljdoc (2)
- # cljs-dev (7)
- # clojure (126)
- # clojure-berlin (1)
- # clojure-conj (4)
- # clojure-dev (1)
- # clojure-germany (12)
- # clojure-italy (22)
- # clojure-spec (96)
- # clojure-uk (111)
- # clojurescript (27)
- # core-async (8)
- # cursive (17)
- # datomic (26)
- # devops (5)
- # editors (15)
- # emacs (13)
- # events (1)
- # figwheel-main (27)
- # fulcro (64)
- # hyperfiddle (29)
- # jobs (8)
- # jobs-discuss (7)
- # liberator (4)
- # off-topic (46)
- # om (9)
- # onyx (1)
- # overtone (1)
- # perun (8)
- # re-frame (28)
- # reagent (35)
- # reitit (5)
- # shadow-cljs (96)
- # spacemacs (1)
- # testing (10)
- # timbre (8)
- # tools-deps (63)
- # unrepl (1)
- # yada (10)
@fabrao there's a page in the wiki related to emacs and putting autosave files in a global/user directory
I still can't understand how to use sift
correctly.
I have a simple task: build a JAR consisting of compiled Java classes and raw Clojure sources.
My intuition suggests this:
(comp (javac)
(sift :add-resource #{"src"} :include #{#"\.clj$"})
(pom :version version)
(jar))
But it seems like :add-resource
(or any other :add-*
) overwrites the current fileset. Is this an expected behavior and does it have to be?
Also, how can I debug which sections are there on the fileset? show :fileset true
doesn't tell that.