It's not a secret anymore!
The moose likes Testing and the fly likes JUnit and logging = exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "JUnit and logging = exception" Watch "JUnit and logging = exception" New topic

JUnit and logging = exception

Heiko Graf

Joined: Jan 10, 2008
Posts: 6
Greetings rangers.
I stumbeld upon this exception, when I start my test with;

LogConfigurationException: invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed

This does not happen, when I use textui instead of swingui, but the text output for failed tests is dreadfull.

Google doesn't help much on this, so I would like to ask, if someone of you knows how I could fix it.

I'm using java 1.4, JUnit 3.8.1 and Oracle JDeveloper
Java 1.5 and Eclipse are both not an option for me at the moment.

Klingon multitasking systems do not support "time-sharing". When a Klingon program wants to run, it challenges the scheduler in hand-to-hand combat and owns the machine
I agree. Here's the link:
subject: JUnit and logging = exception
It's not a secret anymore!