This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-01
Channels
- # adventofcode (2)
- # announcements (3)
- # babashka-sci-dev (79)
- # beginners (76)
- # biff (2)
- # calva (32)
- # cider (2)
- # clj-kondo (42)
- # clj-on-windows (17)
- # clojure (28)
- # clojure-belgium (1)
- # clojure-berlin (1)
- # clojure-europe (95)
- # clojure-nl (4)
- # clojure-norway (4)
- # clojure-uk (5)
- # clojurescript (27)
- # conjure (5)
- # cursive (3)
- # data-science (16)
- # datomic (67)
- # graalvm (12)
- # hyperfiddle (36)
- # jobs (3)
- # jobs-discuss (1)
- # kaocha (2)
- # klipse (1)
- # leiningen (28)
- # lsp (16)
- # luminus (3)
- # malli (10)
- # nrepl (3)
- # off-topic (57)
- # other-languages (18)
- # re-frame (4)
- # reitit (8)
- # releases (1)
- # remote-jobs (1)
- # scittle (4)
- # shadow-cljs (7)
- # test-check (1)
- # tools-deps (4)
- # vim (11)
- # xtdb (25)
Is there much benefit (or disadvantage) of including the .cpcache
directory when copying over the project to build inside a docker container?
.cpcache
is not currently included in the Git repository (and it doesnt feel like it should be), so its not used in our CI, so this would only be local (if its of use at all). Any thoughts or experiences welcome
inside of there are lots of references to /Users/dan/.m2/…
I suspect all of these paths are either (a) thrown away inside of the docker container so they don’t help at all, or (b) it will be an explicit error.
you'll want to rebuild your .cpcache in the container to make the paths right, so better not to include. (can use clojure -P whatever
to "prepare" the classpath - will include grabbing maven libs, making the classpath cache etc
Ah, that makes lots of sense. thank you.