Hi Glenn, try loading commons-logging in the boot classpath. Most classloaders will check their parents for a class first, and this might prevent the testrunner from loading commons-logging multiple times.
hope that helps, Roland Glenn Murray <[EMAIL PROTECTED]> Sent by: Glenn Murray <[EMAIL PROTECTED]> 20.07.2005 20:30 Please respond to "HttpClient User Discussion" To HttpClient User Discussion <[email protected]> cc Subject Re: HttpClient() throws ExceptionInInitializerError in JUnit swingui On Wed, 20 Jul 2005, Roland Weber wrote: > Hi Glenn, ... It seems that the Swing version of the JUnit > TestRunner somehow loads it's own copy of commons-logging. > ... Hi Roland, Thanks for the reply, it did help, you are right. I found the following message: http://www.mail-archive.com/[email protected]/msg02958.html which indicates a swingui classloader interaction problem and a work-around: Solution: Disable "Reload classes every run" or start JUnit with command line option -noloading before the name of the Testsuite. This was two years ago; I wonder if a fix has been made. Reloading the classes every run is an essential feature of JUnit for me. Cheers, Glenn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
