Scott Heaberlin wrote:
Hmm, are you using commons-logging? (LogFactory) - you might want to post to the jakarta-commons list.
Yes, I'm using commons-logging. And, I'll post to commons-logging as well.
My suggestion would be to make sure you have a 'commons-logging.properties' file in your classpath as well as a log4j.properties (or xml) log4j configuration (referenced within your commons-logging config) in the classpath as you execute your test cases / suites.
Commons-logging is supposed to find log4j.properties file anywhere in the classpath (after checking some environment variables), and this has worked for me before. I have almost exactly the same targets generating logs for a different project. The only real difference (that I see) is the directory structure of the source.
I can post what these structures look like if you think that you might spot something.
If you were using log4j only, (eg, Log myLog = Logger.getLogger(AccountTest.class);) you could skip the commons-logging setup and just make a log4j.properties/xml available in the classpath with a console appender or other suitable appenders.
log4j.properties is in the classpath. I'm using a file appender which should create a file in the same directory as the build.xml (current working directory).
Hope this helps,
This is the first response I've gotten from anyone. It's one of those things that's hard to solve unless you're actually working in the environment. Thanks for the response.
Scott Heaberlin
- Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
