Hi Glenn, > I've verified it on Linux and WinXP with Java 1.5. The Error messsage > complains that "You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed," but > the only one is in commons-logging.jar. Does anyone have a clue to > what is going on here?
It seems that the Swing version of the JUnit TestRunner somehow loads it's own copy of commons-logging. If I remember correctly, you mentioned in a previous mail that you can compile without commons-logging being in the classpath? This may indicate that there is some version of commons- logging available not in the explicit classpath but maybe somewhere in the bootclasspath, or that your compiler invocation supplies an extended classpath you are not aware of. Why or how junit.swingui.TestRunner should load commons-logging, I am unable to tell. It may have it's own copy hidden somewhere, or it may load the one from the classpath into a different classloader than the one which will load HttpClient. I have neither the time nor the environment to track this down. Have you tried to provide commons-logging in the bootclasspath instead of the regular classpath? Then it will be available in a different classloader, which may make a big difference. If that also fails, you can try to run a "Hello World" testcase with commons-logging in the bootclasspath, to see whether junit.swingui.TestRunner chokes by itself even without HttpClient. You can also try to get help from the commons-logging community. I believe they have plenty of experience with classloader problems. hope that helps, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
