Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.1
-
None
-
Unknown
-
Description
Since logback shows a special type of stack trace with the name of the jar files involved, it creates it differently and so printStackTrace is no longer called.