| commit | ab8753f631b56eb2ad958041c34b32467cdbb198 | [log] [tgz] |
|---|---|---|
| author | Volkan Yazıcı <volkan.yazici@gmail.com> | Wed Dec 02 17:07:57 2020 +0100 |
| committer | Volkan Yazıcı <volkan.yazici@gmail.com> | Wed Dec 02 17:07:57 2020 +0100 |
| tree | 2cf8d50adc1ba7cd4686c80700befc6f6575c40b | |
| parent | d7288357f89e01d6d4877ba202e4153dcc31d723 [diff] |
LOG4J2-2966 Revert the usage of ParameterizedMessage.deepToString(). There are a couple of motivations for me to revert this change, but some particular highlights are as follows: - Many of the type check that is performed by deepToString() is already addressed in JsonWriter. - Usage of an external method breaks the self-containment contract of JsonWriter. - deepToString() protects against recursive collections, whereas JsonWriter doesn't. Even using deepToString() in JsonWriter isn't enough to protect it against self-referencing collections; all collection handling methods in JsonWriter needs to be adapted. Hence, rather than a code base where there is partial mitigation for this anomaly, now it is explicit that there is no built-in prevention mechanisms. This behaviour is also in line with the Java standard library, e.g., Arrays.toString().
Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture.
By sending a pull request you grant the Apache Software Foundation sufficient rights to use and release the submitted work under the Apache license. You grant the same rights (copyright license, patent license, etc.) to the Apache Software Foundation as if you have signed a Contributor License Agreement. For contributions that are judged to be non-trivial, you will be asked to actually sign a Contributor License Agreement.
Users should refer to Maven, Ivy, Gradle, and SBT Artifacts on the Log4j web site for instructions on how to include Log4j into their project using their chosen build tool.
Basic usage of the Logger API:
package com.example; import org.apache.logging.log4j.Logger; import org.apache.logging.log4j.LogManager; public class Example { private static final Logger LOGGER = LogManager.getLogger(); public static void main(String... args) { String thing = args.length > 0 ? args[0] : "world"; LOGGER.info("Hello, {}!", thing); LOGGER.debug("Got calculated value only if debug enabled: {}", () -> doSomeCalculation()); } private static Object doSomeCalculation() { // do some complicated calculation } }
And an example log4j2.xml configuration file:
<?xml version="1.0" encoding="UTF-8"?> <Configuration> <Appenders> <Console name="Console" target="SYSTEM_OUT"> <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/> </Console> </Appenders> <Loggers> <Logger name="com.example" level="INFO"/> <Root level="error"> <AppenderRef ref="Console"/> </Root> </Loggers> </Configuration>
The Log4j 2 User's Guide is available here or as a downloadable PDF.
Log4j 2.4 and greater requires Java 7, versions 2.0-alpha1 to 2.3 required Java 6. Some features require optional dependencies; the documentation for these features specifies the dependencies.
Apache Log4j 2 is distributed under the Apache License, version 2.0.
How to download Log4j, and how to use it from Maven, Ivy and Gradle. You can access the latest development snapshot by using the Maven repository https://repository.apache.org/snapshots, see Snapshot builds.
Issues, bugs, and feature requests should be submitted to the JIRA issue tracking system for this project.
Pull request on GitHub are welcome, but please open a ticket in the JIRA issue tracker first, and mention the JIRA issue in the Pull Request.
Log4j requires Apache Maven 3.x. To build from source and install to your local Maven repository, execute the following:
mvn install
We love contributions! Take a look at our contributing page.