From f14d5d05c825ecabecb52fc76d55efacecde0891 Mon Sep 17 00:00:00 2001 From: mdb Date: Fri, 13 Aug 2004 21:24:28 +0000 Subject: [PATCH] When logging stack traces, don't log the message separately and then have the exception repeat it, just start logging the exception on the first log line. It's compact and it allows lgrep to properly filter out whole stack traces. git-svn-id: https://samskivert.googlecode.com/svn/trunk@1485 6335cc39-0255-0410-8fd6-9bcaacd3b74c --- .../src/java/com/samskivert/util/DefaultLogProvider.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/samskivert/src/java/com/samskivert/util/DefaultLogProvider.java b/projects/samskivert/src/java/com/samskivert/util/DefaultLogProvider.java index 0bb9bbe2..a8432922 100644 --- a/projects/samskivert/src/java/com/samskivert/util/DefaultLogProvider.java +++ b/projects/samskivert/src/java/com/samskivert/util/DefaultLogProvider.java @@ -78,7 +78,7 @@ public class DefaultLogProvider implements LogProvider { Integer tlevel = (Integer)_levels.get(moduleName); if (level >= getLevel(moduleName)) { - System.err.println(formatEntry(moduleName, level, t.getMessage())); + System.err.print(formatEntry(moduleName, level, "")); t.printStackTrace(System.err); } }