This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-22
Channels
- # alda (1)
- # aws-lambda (23)
- # beginners (27)
- # boot (156)
- # business (2)
- # carry (4)
- # cider (1)
- # cljsjs (2)
- # cljsrn (29)
- # clojure (170)
- # clojure-austin (35)
- # clojure-czech (8)
- # clojure-dusseldorf (5)
- # clojure-italy (4)
- # clojure-nl (1)
- # clojure-quebec (2)
- # clojure-russia (45)
- # clojure-spec (49)
- # clojure-uk (12)
- # clojurescript (81)
- # component (5)
- # datomic (24)
- # devcards (26)
- # emacs (4)
- # hoplon (4)
- # jobs (1)
- # juxt (5)
- # leiningen (6)
- # luminus (14)
- # mount (26)
- # om (27)
- # om-next (2)
- # onyx (22)
- # pedestal (2)
- # planck (3)
- # proton (5)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (60)
- # spacemacs (12)
- # specter (8)
- # untangled (119)
- # vim (61)
- # yada (36)
using composite profiles (i.e. [:dev {...}]
), if i specify :target-path "docs/0.5.1"
or :clean-targets ^{:protect false} [:target-path "docs/0.5.1"]
, I get the following error:
Deleting non-target project paths ["/.../docs/0.5.1%s"] is not allowed.
Check :clean-targets or override this behavior by adding metadata ->
:clean-targets ^{:protect false} [...targets...]
Error encountered performing task 'clean' with profile(s): 'dev-051'
Deleting non-target project paths ["/.../docs/0.5.1%s"] is not allowed.
Check :clean-targets or override this behavior by adding metadata ->
:clean-targets ^{:protect false} [...targets...]
i don't really know how to proceed, other than to manually remove the build directories
i've started to suspect there's something special about the name "docs", because i only just renamed the directory from "examples" (which cleaned fine), when i started investigating deploying my (cljs) build with github pages
for anyone wondering, i narrowed this down to having an entry in :aliases
cleaning all profiles using lein with-profile every,single,profile clean
i was able to work around it by using lein do ...
, which is more verbose but at least it works
i suspect that whatever leiningen uses to compose profiles is not preserving the ^{:protect false}
metadata