The infamous classloader problem!
It seems IDEA's plugin architecture doesn't create a new "classloader space" for a plugin (like what Tomcat does for each webapp) and IDEA itself is using log4j (and beanutils?). I ran into similar problem with JBuilder and Oracle JDev when I was working on my company's Collage IDE plugins.
Configuring common-logging not to use log4j may be a workaround. I dunno... Otherwise, the IDEA Ant plugin needs to be rewritten to create its own loader space.
--
John
At 10:22 pm 17-01-03, you wrote:
I'm trying to run the Struts JUnit tests under IDEA. They run fine under--
Ant alone, but fail under the IDEA Ant plugin. When I try to run
individual tests, I often see the infamous
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:430)
This also occurs when I try to run any test that uses BeanUtils. (Life is good until I test code that calls BeanUtils, then "oops".) I
traced it down, and the constructor class is failing in the JVM.
I see Log4J in the IDEA lib folder. Could this be conflicting with the
default LogFactory? Do I need to configure Log4J (somehow) to appease the Commons Logging API before running the Struts tests within IDEA?
-Ted.
John Yu Scioworks Technologies
e: [EMAIL PROTECTED] w: +(65) 873 5989
w: http://www.scioworks.com m: +(65) 9782 9610
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
