Thanks for your answers Ceki and Anton, and sorry for the delay to answer.
I will submit an issue as suggested. And sorry for using confusing terms, by logging errors I meant just the ability to print logback errors to sdterr by configuration. Ceki Gulcu-2 wrote: > > Hello Syvalta, > > Thank you for your message. I'd to point out that logback does not and > cannot > *log* from within itself, To be more precise, logback does not generate > logging > requests without solicitation from client code (code outside logback). > There is > actually code within logback that drops log messages generated by logback > components. > > However, logback components are allowed to generate status messages about > their > internal state and add them to the StatusManager associated with the > logback > context. Note that most logback components have a reference to their > context. > > If you wanted to have only Warn and Error status messages printed, you > could > write your own StatusManager that does just that. Unfortunately, at > present time > you cannot tell LoggerContext to use a StatusManager different than the > default. > > If you kindly enter a Jira issue asking for this feature, I'd be happy to > oblige. > -- View this message in context: http://www.nabble.com/How-to-get-log-configuration-errors-logged-but-not-debug--tp17780728p18959201.html Sent from the Logback User mailing list archive at Nabble.com. _______________________________________________ Logback-user mailing list [email protected] http://qos.ch/mailman/listinfo/logback-user
