This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-25
Channels
- # admin-announcements (5)
- # arachne (1)
- # beginners (29)
- # boot (36)
- # cider (110)
- # clara (1)
- # cljs-dev (3)
- # cljs-edn (14)
- # cljsrn (24)
- # clojure (63)
- # clojure-belgium (3)
- # clojure-dusseldorf (5)
- # clojure-greece (9)
- # clojure-russia (142)
- # clojure-sg (15)
- # clojure-uk (20)
- # clojurebridge (4)
- # clojurescript (58)
- # data-science (1)
- # datomic (37)
- # editors (2)
- # editors-rus (7)
- # emacs (1)
- # garden (31)
- # hoplon (3)
- # jobs-discuss (8)
- # keechma (86)
- # leiningen (1)
- # liberator (2)
- # mount (23)
- # off-topic (2)
- # om (18)
- # onyx (42)
- # planck (1)
- # quil (6)
- # re-frame (8)
- # reagent (3)
- # ring-swagger (1)
- # specter (4)
- # untangled (1)
hello, I’m using boot
in [rum-mdl](https://github.com/aJchemist/rum-mdl) project. This would be another example of build.boot
.
My boot dev
task appears to no longer do hot reloading, is there any way I can debug this?
How can I investigate that kind of exceptions with boot when running a boot task ? Is there a way to recover the boot.user temp file ?
@jethroksy: I do (reset)
manually
I have several components, and I guess restarting just the web server would make my workflow more efficient
I think I know how to go about that, just wondering what the general approach to the problem is
Is there a way to get a better error report than this exception stack i'm getting with boot ?
should I fill a bug report ? I get the previously mentionned exception when verbose flag is up on the watch task, which stops the dev task, while it works normally without it
What’s the preferred way to include .java files into a build? I’ve added vendor/src to source-paths and am calling javac (which works for our dev env) but it fails in the test env.
We’re using quartz (clojurequartz) which is a wrapper for the quartz scheduler.
The tests can’t find the java class which is present in dev.
Are directories created by tmp-dir!
automagically cleaned up after the boot process closes?
@clem: I don't think it's fully cleaning all used tmp-dirs
you'll see a file in the temp dirs called .deleteme
which is what boot uses to know which ones can be deleted
@micha ok, makes sense. I was wondering what the protocol was for task writers cleaning up after themselves. I take it most just leave the temporary directory?