You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2015/08/12 17:58:56 UTC

logging-log4j2 git commit: Update migration guide to mention Configurator.setLevel().

Repository: logging-log4j2
Updated Branches:
  refs/heads/master eb0f9a2b3 -> d66b7e4cb


Update migration guide to mention Configurator.setLevel().

Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/d66b7e4c
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/d66b7e4c
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/d66b7e4c

Branch: refs/heads/master
Commit: d66b7e4cb0ef9d375f65e7d82d236462a93a45e9
Parents: eb0f9a2
Author: ggregory <gg...@apache.org>
Authored: Wed Aug 12 08:58:48 2015 -0700
Committer: ggregory <gg...@apache.org>
Committed: Wed Aug 12 08:58:48 2015 -0700

----------------------------------------------------------------------
 src/site/xdoc/manual/migration.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/d66b7e4c/src/site/xdoc/manual/migration.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/manual/migration.xml b/src/site/xdoc/manual/migration.xml
index 7caf0ff..34b9d2a 100644
--- a/src/site/xdoc/manual/migration.xml
+++ b/src/site/xdoc/manual/migration.xml
@@ -76,7 +76,8 @@
                 <li>
                   Calls to <code>org.apache.log4j.Logger.setLevel()</code> or similar methods are not supported in the API.
                   Applications should remove these. Equivalent functionality is provided in the Log4j 2 implementation
-                  classes but may leave the application susceptible to changes in Log4j 2 internals.
+                  classes, see <code>Configurator.setLevel()</code>,  but may leave the application susceptible to changes in 
+                  Log4j 2 internals.                   
                 </li>
                 <li>
                   Where appropriate, applications should convert to use parameterized messages instead of String