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

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

though not ideal

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?

@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

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

right on

@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?

@dergutemoritz an issue would be great: https://issues.jboss.org/browse/IMMUTANT

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

Ah here it is: https://issues.jboss.org/browse/IMMUTANT-630

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

Oh well, Jira ...

immutanters.

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

@jrotenberg yo!

@tcrawley howzit?

i miss immutant

@tcrawley Makes sense 🙂

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

yeah, pretty good overall

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

had a good time in austin, though