Project Alternative log4j Configuration: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
For command-line utilities that run in foreground and want to route their all log4j logging information to stderr if -v or --verbose command line options are used, see: {{Internal|Project log4j Debugging on --verbose|Project log4j Debugging on --verbose}} | For command-line utilities that run in foreground and want to route their all log4j logging information to stderr if -v or --verbose command line options are used, see: {{Internal|Project log4j Debugging on --verbose|Project log4j Debugging on --verbose}} | ||
[[Project log4j Debugging on --verbose|log4j Debugging on --verbose]] and | [[Project log4j Debugging on --verbose|log4j Debugging on --verbose]] and alternative log4j configuration can be combined, where --verbose flag applies until the configuration file is parsed and the new logging configuration is installed. | ||
Revision as of 15:54, 23 July 2017
Internal
Overview
A pattern that consists in accepting alternative log4j configuration for applications that run in background. The application rely on a base log4j configuration file, usually shipped as part of the application's installation bundle, but it can change its logging behavior based on logging configuration present in the application's configuration file. Configuration that comes from the application's configuration file takes priority over configuration stored in log4j.xml.
For command-line utilities that run in foreground and want to route their all log4j logging information to stderr if -v or --verbose command line options are used, see:
log4j Debugging on --verbose and alternative log4j configuration can be combined, where --verbose flag applies until the configuration file is parsed and the new logging configuration is installed.