Reload4j
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
 |
Reload4j was created by the original author of log4j 1.x, Ceki Gulcu. Reload4j is a fork of log4j version 1.2.17. It preserves the same java name space, that is "org.apache.log4j". However, is is published under the "ch.qos.reload4j" group id in Maven Central.
The aim of the reload4j project is to provide a migration path to those users wishing to correct log4j 1.x security issues. Upgrading to a newer version of log4j 1.x is not possible since the project has been declared EOL [1] by the Apache Software Foundation. This decision was reaffirmed in 2022[2]. Moreover, log4j 2.x has a considerably different API and configuration style.
Version 1.2.8.0 of reload4j was released on the 12th of January 2022 and is available for public consumption.
Subsequently, the SLF4J project has released SLF4J version 1.7.33[3] with support for reload4j via the slf4j-reload4j module.
More information is available on the project web site.
 | This redirect has not been added to any content categories. Please help out by adding categories to it so that it can be listed with similar redirects, in addition to a stub category. (January 2022) |
- ^ "Apache™ Logging Services™ Project Announces Log4j™ 1 End-Of-Life; Recommends Upgrade to Log4j 2". Apache Logging Services.
- ^ Ron, Grabowski (2022-01-06). "Log4j 1 End-of-Life Statement". lists.apache.org. Apache Logging Services.
{{cite web}}: CS1 maint: url-status (link) - ^ SLF4J.ORG (2022-01-13). "Release of version 1.7.33". SLF4J. SLF4J.ORG.
{{cite web}}: CS1 maint: numeric names: authors list (link)