Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace log4j:WARN with reload4j:WARN #69

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ppkarwasz
Copy link
Contributor

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` and `reload4j`.

This commit helps user distinguish the backend that is actually used.
@ppkarwasz
Copy link
Contributor Author

ppkarwasz commented Oct 12, 2023

The CI failures are probably unrelated to these changes. The test should use the SO_REUSEADDR socket option or switch to ephemeral ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant