You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rg...@apache.org on 2019/01/05 22:16:14 UTC

[logging-log4j2] branch release-2.x updated: Promote the Log4j API

This is an automated email from the ASF dual-hosted git repository.

rgoers pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/release-2.x by this push:
     new 0e23940  Promote the Log4j API
0e23940 is described below

commit 0e23940fc0d3cb106ef171cde4896e5aa48c2260
Author: Ralph Goers <rg...@apache.org>
AuthorDate: Sat Jan 5 15:16:05 2019 -0700

    Promote the Log4j API
---
 src/site/markdown/index.md.vm | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
index b27fa87..36a42ce 100644
--- a/src/site/markdown/index.md.vm
+++ b/src/site/markdown/index.md.vm
@@ -32,6 +32,17 @@ The API for Log4j is separate from the implementation making it clear for applic
 methods they can use while ensuring forward compatibility. This allows the Log4j team to improve the implementation
 safely and in a compatible manner.
 
+The Log4j API is a logging facade that may, of course, be used with the Log4j implementation, but may also be used
+in front of other logging implementations such as Logback. The Log4j API has several advantages over SLF4J:
+1. The Log4j API supports logging [Messages](manual/messages.html) instead of just Strings.
+2. The Log4j API supports lambda expressions.
+3. The Log4j API provides many more logging methods than SLF4J.
+4. In addition to the "parameterized logging" format supported by SLF4J, the Log4j API also supports events using
+the java.text.MessageFormat syntax as well printf-sytle messages.
+5. The Log4j API provides a LogManager.shutdown() method. The underlying logging implementation must implement the
+Terminable interface for the method to have effect.
+6. Other constructs such as Markers, log Levels, and ThreadContext (aka MDC) are fully supported.
+
 $h3 Improved Performance
 
 Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios