Since the original log4j:log4j Maven artifact is still a quite common transitive dependency, an application might easily end up with both Log4j 1.2 and Reload4j.
The log messages used by Reload4j are identical to those generated by Log4j 1.2 and even point to the same documentation. This can confuse users that end up with multiple SLF4J backends in their runtime. I have seen multiple question on SO due to this, the most recent is Why log4j can't find the configuration file.
Changing the status logger prefix to "reload4j" and redirecting to https://reload4j.qos.ch/faq.html could save some debugging time to users.
Since the original
log4j:log4j
Maven artifact is still a quite common transitive dependency, an application might easily end up with both Log4j 1.2 and Reload4j.The log messages used by Reload4j are identical to those generated by Log4j 1.2 and even point to the same documentation. This can confuse users that end up with multiple SLF4J backends in their runtime. I have seen multiple question on SO due to this, the most recent is Why log4j can't find the configuration file.
Changing the status logger prefix to "reload4j" and redirecting to https://reload4j.qos.ch/faq.html could save some debugging time to users.