Project log4j Debugging on --verbose: Difference between revisions
Jump to navigation
Jump to search
Line 41: | Line 41: | ||
<pre> | <pre> | ||
verbose=false | verbose=false | ||
... | ... | ||
${verbose} && verbose_system_property="-Dverbose=true" | ${verbose} && verbose_system_property="-Dverbose=true" | ||
command="${java_bin} ... ${verbose_system_property} ${main_class}..." | command="${java_bin} ... ${verbose_system_property} ${main_class}..." | ||
</pre> | </pre> |
Revision as of 01:20, 8 August 2016
Internal
Overview
This is a development pattern that routes log4j logging information to stderr if -v|--verbose command line option is used. Projects that implement it are clad, os-stats, etc.
Procedure
Use novaordis-utilities 4.2 or newer. novaordis-utilities 4.2.0 was the first release that contains StderrVerboseLogging.
For more details, see:
Activate it as follows:
import io.novaordis.utilities.logging.StderrVerboseLogging; ... if (verbose) { StderrVerboseLogging.enable(); } ...
The recommended way to pass the "verbose" information that was already identified by a bash wrapper to the JVM is to use:
-Dverbose=true
Typical bash wrapper code:
verbose=false ... ${verbose} && verbose_system_property="-Dverbose=true" command="${java_bin} ... ${verbose_system_property} ${main_class}..."