Author: rpopma
Date: Fri Jun 20 14:08:23 2014
New Revision: 1604173
URL: http://svn.apache.org/r1604173
Log:
LOG4J2-141 improved documentation regarding log4j status logger
Modified:
logging/log4j/log4j2/trunk/src/changes/changes.xml
logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm
Modified: logging/log4j/log4j2/trunk/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/changes/changes.xml?rev=1604173&r1=1604172&r2=1604173&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/changes/changes.xml (original)
+++ logging/log4j/log4j2/trunk/src/changes/changes.xml Fri Jun 20 14:08:23 2014
@@ -22,6 +22,9 @@
</properties>
<body>
<release version="2.0-rc2" date="2014-MM-DD" description="Bug fixes and
enhancements">
+ <action issue="LOG4J2-141" dev="rpopma" type="fix" due-to="Joern
Huxhorn">
+ Improved documentation regarding log4j status logger.
+ </action>
<action issue="LOG4J2-539" dev="rpopma" type="fix" due-to="Colin
Froggatt">
Fixed issue with "Reconfigure using XML below" function in JMX Client
GUI.
ConfigurationSource is now a top-level class and can be obtained with
Configuration.getConfigurationSource().
Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm
URL:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm?rev=1604173&r1=1604172&r2=1604173&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm
(original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/configuration.xml.vm Fri
Jun 20 14:08:23 2014
@@ -389,7 +389,11 @@ public class Bar {
</tr>
<tr>
<td>status</td>
- <td>The level of internal Log4j events that should be logged
to the console.</td>
+ <td>The level of internal Log4j events that should be logged
to the console.
+ Valid values for this attribute are "trace", "debug", "info",
"warn", "error" and "fatal".
+ Log4j will log details about initialization, rollover and
other internal actions to the status logger.
+ Setting <tt>status="trace"</tt> is one of the first things
tools available to you if you need to
+ troubleshoot log4j.</td>
</tr>
<tr>
<td>strict</td>
