Hi Chetan, Thanks for following through on this. I think the loss of messages during initialization is less than ideal, but acceptable and certainly understandable.
Justin On Thu, Feb 6, 2014 at 1:34 AM, Chetan Mehrotra <[email protected]> wrote: > Just an update. The issue has now been fixed on Slf4j side and a new > release 1.7.6 was made which contains the fix. So this completes the > #3 approach mentioned previously. > > With this there is just a small issue that while Slf4j is getting > initialized the log message would get lost as at that time NOP Loggers > are used. Once initialization is complete the log message from such > loggers would be handled in default way. To fix this we would need to > control the startup order and get the Commons Log bundle started > first. > Chetan Mehrotra > > > On Wed, Jan 29, 2014 at 4:47 PM, Chetan Mehrotra > <[email protected]> wrote: >> On Wed, Jan 29, 2014 at 4:39 PM, Carsten Ziegeler <[email protected]> >> wrote: >>> never ever rely on that. >> Agreed. But ... >> >>>And for B we would need changes at least in the launchpad - for A we just >> fix slf4j >> Change in our code is in our control and easy to do without incurring >> any penalty. Fix in Slf4j might take time. So its like a workaround >> untill proper fix is done. >> >> Chetan Mehrotra
