Repository: logging-log4j2 Updated Branches: refs/heads/master 8852cd163 -> f2d56bee1
Better style with <code> tags. Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/f2d56bee Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/f2d56bee Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/f2d56bee Branch: refs/heads/master Commit: f2d56bee1a753630103bf5291072ba32024b2359 Parents: 8852cd1 Author: Gary Gregory <[email protected]> Authored: Tue May 2 13:15:08 2017 -0700 Committer: Gary Gregory <[email protected]> Committed: Tue May 2 13:15:08 2017 -0700 ---------------------------------------------------------------------- src/site/xdoc/manual/api.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/f2d56bee/src/site/xdoc/manual/api.xml ---------------------------------------------------------------------- diff --git a/src/site/xdoc/manual/api.xml b/src/site/xdoc/manual/api.xml index 15dc6df..5ecfa45 100644 --- a/src/site/xdoc/manual/api.xml +++ b/src/site/xdoc/manual/api.xml @@ -138,13 +138,14 @@ logger.trace("Some long-running operation returned {}", () -> expensiv <h4>Logger Names</h4> <p> Most logging implementations use a hierarchical scheme for matching logger names with logging - configuration. In this scheme the logger name hierarchy is represented by '.' characters in the - logger name, in a fashion very similar to the hierarchy used for Java package names. For example, - org.apache.logging.appender and org.apache.logging.filter both have org.apache.logging as their parent. - In most cases, applications name their loggers by passing the current class's name to - LogManager.getLogger. Because this usage is so common, Log4j 2 provides that as the default when - the logger name parameter is either omitted or is null. For example, in all examples below the Logger will - have a name of "org.apache.test.MyTest". + configuration. In this scheme the logger name hierarchy is represented by <code>'.'</code> characters + in the logger name, in a fashion very similar to the hierarchy used for Java package names. For example, + <code>org.apache.logging.appender</code> and <code>org.apache.logging.filter</code> both have + <code>org.apache.logging</code> as their parent. In most cases, applications name their loggers by + passing the current class's name to <code>LogManager.getLogger(...)</code>. Because this usage is so + common, Log4j 2 provides that as the default when the logger name parameter is either omitted or is + null. For example, in all examples below the Logger will have a name of + <code>"org.apache.test.MyTest"</code>. </p> <pre class="prettyprint linenums">package org.apache.test;
