Originally posted by Jeff Black:
so if we can configure the logging framework via code to capture the messages in memory, that would work out fairly well.
You might be able to get by just by having a different configuration file for test vs. production. For example, I've had separate source trees for production code and test code and separate "resource" directories as well, meaning that I could do things like:
Now, when you configure your build/IDE to put the stuff in "src/test/*" before "src/main/*" to your classpath, the test configuration will be used when you run tests. When you package up the application for deployment, however, you exclude "src/test/*" altogether and end up with the production configuration.