Looking at the last JUnit test case I wrote, I called log4j's BasicConfigurator.configure() method inside the class constructor. That worked fine for running just that single class from Eclipse's "run ...
I'm newly using log4j in a project. A fellow programmer told me that using System.out.println is considered bas style and that log4j is something like standard for logging matters nowadays.
We do ...
For some reason my Eclipse console no longer displays Log4j INFO and DEBUG statements when I run JUnit tests.
In terms of code there hasn't been any change, so it must something ...
is there a standard configuration regarding logging with log4j in JUnit using Eclipse?
When I create a new JUnit-Test testing a class which uses a Logger I don't have to change the ...
In running some JUnit tests I start with the following to set up Log4J:
BasicConfigurator.configure()
I'm then calling the following via Commons Logging:
LogFactory.getLogger(this.getClass()).fatal(exception)
This doesn't print stack traces though (only the exception message).
I ...