Another FYI, I've been able to create an uberjar with boot and boot-tools-deps (for a very cool project btw) https://github.com/dundalek/closh/pull/90/files#diff-0a1425bd66240468daf4c256a411ce75
There were some issues with a git dependency (tools.reader) that had to be excluded to not pull in another tools.reader versions (see https://github.com/dundalek/closh/blob/master/deps.edn#L3)
The problematic behaviour i saw was similar to an old (boot?) problem I found https://clojurians-log.clojureverse.org/boot/2016-02-04/1454607628.002739
@tolitius ^ Not sure if this is still interesting for you 2 years later, and also not sure if it has the same cause
Do people know closh btw? I thought about it a bit and I think there could be a very nice synergy between closh and boot (imagine a boot shell..?)
thanks Jeroen, it might have very well be it two years ago. I left those projects in lein, since they were not exactly standard, rpm based projects and had other issues, but thanks for linking me back in case I see this again
Hello all, I´m trying to use boot-expectations
and I´m having some problems. What is it means?
"`(set-env! :source-paths #{"test"}) `
You will need to do this outside the middleware layer of any prior task since boot-expectations creates a pod based on the dependencies outside its middleware layer for efficiency."
@fabrao If you're just using expectations
as a top-level task, you don't need to worry about it. It's just a caveat for when you're composing tasks. If you have to ask what it means, you don't need to worry about it (yet).
hello all, what´s the problem using boot-expectations
giving file not found about <some_file>_test.clj? I included :source-paths #{"src/clj" "src/cljs" "test/clj"}
source test for it
in set-env!
@fabrao What is the namespace in that file? (in the ns
form)
src/clj/db/notificacao/regra.clj
for source and test/clj/db/notificacao/regra_test.clj
(ns db.notificacao.regra)
and (ns db.notificacao.regra-test)
Those look correct. Is this project up on GitHub where we can look at it?
If not, maybe you can at least share your build.boot
file?
the project is not in git, it´s local.
buil.boot:
`
text too long?
why boot watch expectations
runs not only when I save the file?
If I type something to file, the test runs ... Emacs autosaving?
@fabrao sounds like it
the solution is, stop autosaving?
It didn´t work