[jira] Commented: (LOGGING-25) [logging] call to getClassLoader() in LogFactoryImpl not checked for null

2006-12-19 Thread David Smiley (JIRA)
[ http://issues.apache.org/jira/browse/LOGGING-25?page=comments#action_12459646 ] David Smiley commented on LOGGING-25: - Sorry... it appears that the problem was with v1.0.4 and not 1.1 or later. I *thought* I tried 1.1 in my environment

[jira] Commented: (LOGGING-25) [logging] call to getClassLoader() in LogFactoryImpl not checked for null

2006-12-16 Thread Simon Kitching (JIRA)
[ http://issues.apache.org/jira/browse/LOGGING-25?page=comments#action_12459088 ] Simon Kitching commented on LOGGING-25: --- Applying this patch would cause some undesirable side-effects. For example, method logClassLoaderEnvironment uses

[jira] Commented: (LOGGING-25) [logging] call to getClassLoader() in LogFactoryImpl not checked for null

2006-12-08 Thread David Smiley (JIRA)
[ http://issues.apache.org/jira/browse/LOGGING-25?page=comments#action_12456938 ] David Smiley commented on LOGGING-25: - FYI, here's the new code that should go into the try/catch block: ClassLoader result =

[jira] Commented: (LOGGING-25) [logging] call to getClassLoader() in LogFactoryImpl not checked for null

2006-12-07 Thread David Smiley (JIRA)
[ http://issues.apache.org/jira/browse/LOGGING-25?page=comments#action_12456614 ] David Smiley commented on LOGGING-25: - This hasn't been fixed. This problem can be seen using Apple's VM on Mac OS X if JCL is on the bootclasspath (such as