We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Log4j have release 2.24.2 solving apache/logging-log4j2#3143 - which can cause LogManager.getLogger() to return null under certain conditions.
LogManager.getLogger()
The release notes for 2.24.1 (currently in use in spring-boot 3.4.0) was retrofitted with a warning encouraging the upgrade.
Log4j 2.x release notes: https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-24-2
The text was updated successfully, but these errors were encountered:
Thanks but we don't need an issue for a dependency upgrade such as this. As explained in the issue template that was displayed when you opened this issue, we have some semi-automated tooling that will handle it.
Sorry, something went wrong.
Sorry, it was my mistake not reading the template all the way through... Thanks for the fail-fast response!
No branches or pull requests
Log4j have release 2.24.2 solving apache/logging-log4j2#3143 -
which can cause
LogManager.getLogger()
to return null under certain conditions.The release notes for 2.24.1 (currently in use in spring-boot 3.4.0) was retrofitted with a warning encouraging the upgrade.
Log4j 2.x release notes: https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-24-2
The text was updated successfully, but these errors were encountered: