Fork me on GitHub
#boot
<
2016-08-06
>
underplank03:08:28

Hi all. Is there instructions on uninstalling boot? I think I hand installed it at some point, and now want to install the brew version.

flyboarder03:08:48

@underplank: You should be fine with just deleting the binary, you can also clear the ~/.boot/ directory

underplank03:08:42

oh great. that makes it easy 🙂

fossifoo09:08:04

i'm trying to write a boot task for cloverage and that was pretty simple as a core task, but i want to stick it into a pod because it uses a weird version of the reader most likely to cause problems for some projects

fossifoo09:08:12

it uses (.getResourceAsStream (clojure.lang.RT/baseLoader) [...]) to get it's (re)sources and i wonder how i get the sources of the project itself into the env of the pod

fossifoo09:08:31

this might be a little over my head for a first boot task XD

fossifoo09:08:56

ah https://github.com/adzerk-oss/boot-test/blob/master/src/adzerk/boot_test.clj uses

(pod/with-eval-in worker-pod
                          (doseq [ns '~namespaces] (require ns))
is that idiomatic?

fossifoo09:08:24

seems like it. is there any practical difference to (.require pod ^String ns) beforehand?

fossifoo14:08:34

what is the usual handling for test namespaces? do people put them into :source-paths or not?

anmonteiro14:08:30

@fossifoo: normally I just make a task for that

(deftask testing []
  (set-env! :source-paths #(conj % "test"))
  identity)

anmonteiro14:08:04

then the task that actually runs the tests is just (comp (testing) (boot-test/test))

fossifoo14:08:23

hmm, so with a cloverage task, where would you expect to pass that in?

fossifoo14:08:54

is it usual to pass such things via the env? or rather as a parameter to the task?

fossifoo14:08:27

man, this lettle boot excursion sure escalated quicker into an involved project than i expected XD

martinklepsch14:08:13

It's more common to have a testing task as Antonio described than having a task that adds another directory via an option

fossifoo14:08:47

i'm in the process of writing a "cloverage" task for measuring code coverage and that needs that information as well because you only want "main" code to be instrumented and reported

fossifoo14:08:30

so if i go with the above, i can not really know which ones are which

fossifoo14:08:48

other than (comp (testing) (boot-cloverage/coverage :s "test"))`

fossifoo14:08:03

which would kinda repeat that directory

anmonteiro14:08:34

@fossifoo: I don’t really know how the internals of cloverage work, but can’t you assume you’ll have all the info you need in your task?

anmonteiro14:08:45

then it’s a user concern to actually get source paths right

anmonteiro14:08:58

It’s how most tasks work, if I understand correctly

martinklepsch15:08:41

@fossifoo: ah you mean like you need to know if a file comes from a test or source directory?