Hi, We weren't always supplying the original exception that caused the LogManager to print a warning. Which helps debugging issues as reported in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27857 This patch adds them in all cases:
2006-06-01 Mark Wielaard <[EMAIL PROTECTED]> * java/util/logging/LogManager.java (createInstance): Always add original exception on warning. Committed, Mark
Index: java/util/logging/LogManager.java =================================================================== RCS file: /cvsroot/classpath/classpath/java/util/logging/LogManager.java,v retrieving revision 1.21 diff -u -r1.21 LogManager.java --- java/util/logging/LogManager.java 28 May 2006 08:58:32 -0000 1.21 +++ java/util/logging/LogManager.java 1 Jun 2006 17:03:12 -0000 @@ -836,11 +836,11 @@ } catch (ClassNotFoundException e) { - warn(property, className, "class not found"); + warn(property, className, "class not found", e); } catch (IllegalAccessException e) { - warn(property, className, "illegal access"); + warn(property, className, "illegal access", e); } catch (InstantiationException e) { @@ -848,7 +848,7 @@ } catch (java.lang.LinkageError e) { - warn(property, className, "linkage error"); + warn(property, className, "linkage error", e); } return null;
signature.asc
Description: This is a digitally signed message part