Changing where to log (file, console, etc) and the output verbosity level will be easier to configure if we implement support for log4j 2.
Working on a unit test, I was able to see annoying informational output messages that could be suppressed when running the tests using a different log4j configuration file than the one that should be used in production.
Changing where to log (file, console, etc) and the output verbosity level will be easier to configure if we implement support for log4j 2.
Working on a unit test, I was able to see annoying informational output messages that could be suppressed when running the tests using a different log4j configuration file than the one that should be used in production.