Fork me on GitHub
#boot
<
2017-04-08
>
thosmos02:04:37

@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

fatihict16:04:41

Hello folks, I am using this library fzakaria/slf4j-timbre to configure all my logging with Timbre.

fatihict16:04:18

I am not able to configure logging from inside certain boot tasks. I think it has to do with isolated class paths.

fatihict16:04:30

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?

micha16:04:54

logging is crazy

micha16:04:03

on the jvm

fatihict16:04:47

Yeah, I know πŸ˜›. I spent the last 3 days working on logging issues πŸ˜„

micha16:04:37

logging from 3rd party code is the worst πŸ™‚

micha16:04:15

have you tried making the logback.xml file or whatever in your :resource-paths?

micha16:04:36

that should be on the classpath in tasks pods

micha16:04:42

at least for all the tasks i know of

micha16:04:09

and i think that file will override the default configurations for the 3rd party loggers

micha16:04:39

i have never had full success with configuring logging programmatically

fatihict16:04:11

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.

micha16:04:55

yeah i could not figure out the runtime relationships well enough to get any kind of runtime configuration of loggers to work properly

micha16:04:24

also i started to want to flip tables

fatihict16:04:37

Hahahah πŸ˜†

richiardiandrea19:04:39

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