This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-08
Channels
- # architecture (8)
- # boot (18)
- # cider (33)
- # cljs-dev (35)
- # cljsrn (3)
- # clojure (77)
- # clojure-dev (6)
- # clojure-dusseldorf (1)
- # clojure-russia (1)
- # clojure-spec (4)
- # clojurescript (40)
- # cryogen (1)
- # cursive (4)
- # dirac (2)
- # emacs (1)
- # figwheel (10)
- # funcool (2)
- # hoplon (21)
- # incanter (2)
- # leiningen (1)
- # lumo (44)
- # off-topic (2)
- # onyx (53)
- # overtone (5)
- # pedestal (8)
- # re-frame (9)
- # reagent (37)
- # rum (9)
- # spacemacs (16)
- # sql (2)
- # testing (1)
- # unrepl (4)
- # untangled (4)
- # yada (16)
@timgilbert yes those will be passed to output, whereas files in :source-paths
wonβt. https://github.com/boot-clj/boot/wiki/Filesets#fileset-components
Hello folks, I am using this library fzakaria/slf4j-timbre
to configure all my logging with Timbre
.
I am not able to configure logging from inside certain boot tasks. I think it has to do with isolated class paths.
The logging from third party libraries are being managed by timbre, but with the default config of timbre instead of the one I have defined. Is it possible to make boot tasks use my config instead?
and i think that file will override the default configurations for the 3rd party loggers
We were already managing our logging with a logback.xml file and that was working for tasks pods. Then some library we depend on used Timbre which we didn't see in our output, so I tried to let everything be managed by Timbre and the solution I have right now is back to logback with Timbre writing to Java loggers.
yeah i could not figure out the runtime relationships well enough to get any kind of runtime configuration of loggers to work properly
I found out that for me the best solution was to tunnel everything to log4j2 and get rid of Timbre back when I was working on lambone