Fork me on GitHub
#immutant
<
2017-05-03
>
tcrawley15:05:07

@dergutemoritz I took a look, and it is difficult for Immutant to solve this for you automatically

tcrawley15:05:32

however, handling it in your application code is possible: https://gist.github.com/435fcc19fff9eab62915f960ef014947

tcrawley15:05:39

though not ideal

rauh16:05:36

So I'm initializing my logback programatically. Not using a logback.xml. Which works, but as soon as immutant gets initalized it seems to re-init logging to its own default. I fixed it now by re-init'ing the logging after immutant gets run. But: Is there a way to tell it not to mess at all with the logging config?

tcrawley17:05:34

@rauh currently, no. There's no switch to prevent it from re-initializing, though it wouldn't be difficult to to add a sysprop to prevent that, maybe

rauh17:05:24

@tcrawley No worries, I'm probably a minority here and no reason to add complexity.

dergutemoritz21:05:47

@tcrawley Thanks for checking. Yeah, that workaround is pretty much what I came up with and I don't like it much either 🙂 Should I file an issue for that somewhere? If so, where?

dergutemoritz22:05:03

@tcrawley Odd, I just submitted one but it's not showing up anywhere

dergutemoritz22:05:05

Oddly it's not showing up under "My open issues" but it does under "Reported by me".

dergutemoritz22:05:08

Oh well, Jira ...

jrotenberg22:05:02

immutanters.

tcrawley22:05:51

@dergutemoritz I think it has to be assigned to you to show under your open issues

jrotenberg22:05:50

i miss immutant

tcrawley23:05:14

@jrotenberg good good! How are you, my friend?

jrotenberg23:05:13

yeah, pretty good overall

jrotenberg23:05:33

i missed the conj, but some of my colleagues were there

jrotenberg23:05:38

had a good time in austin, though