By the way I checked to add %ex as suggested on this comment : Ceki Gulcu added a comment - 08/Sep/11 11:02 PM
It removes the display of package info but there is still the exception stack trash in the console.
Additionally it seems the static initializer of PackagingDataCalculator will cause problems as well (as in bug 472) :
Let's assume the class is loaded with permissions, then the boolean GET_CALLER_CLASS_METHOD_AVAILABLE will have the value true.
Then an execption in the tested code is thrown and logged without privileges => populateFrames() will be called and will throw another another uncaught AccessControlException (to be checked...).
http://jira.qos.ch/browse/LOGBACK-472
By the way I checked to add %ex as suggested on this comment : Ceki Gulcu added a comment - 08/Sep/11 11:02 PM
It removes the display of package info but there is still the exception stack trash in the console.
Additionally it seems the static initializer of PackagingDataCalculator will cause problems as well (as in bug 472) :
Let's assume the class is loaded with permissions, then the boolean GET_CALLER_CLASS_METHOD_AVAILABLE will have the value true.
Then an execption in the tested code is thrown and logged without privileges => populateFrames() will be called and will throw another another uncaught AccessControlException (to be checked...).