Bump org.apache.logging.log4j:log4j-bom from 2.20.0 to 2.24.3

[dependabot]

Bumps org.apache.logging.log4j:log4j-bom from 2.20.0 to 2.24.3.

Release notes

Sourced from org.apache.logging.log4j:log4j-bom's releases.

2.24.3

Release Notes

This release fixes two minor bugs.

• Fix ConcurrentModificationException, if multiple threads modify loggers concurrently. This bug affects users that modify logger levels programmatically. (#3234)
• Protects PropertiesUtil against property sources that call PropertiesUtil recursively. In some cases such a property source can even cause deadlocks. (#3252)

2.24.2

Release Notes

This release fixes a critical bug in Log4j API initialization code, which can cause LogManager.getLogger() to return null under certain conditions. See #3143 for details.

Fixed

• Fix key removal issues in Thread Context (#3048)
• Use hard references to Loggers in LoggerRegistry. (#3143)
• Fix ArrayIndexOutOfBoundsException in JSON Template Layout truncated exception resolver (#3216)

2.24.1

This release contains mainly bug fixes of problems encountered with the thread context map, logger registry and configuration reloading.

It also enhances integration tests to use Docker images of the most recent releases of MongoDB and Elastic Search.

Changed

• Rework LoggerRegistry to make it MessageFactory-namespaced. This effectively allows loggers of same name, but different message factory. (#2936)
• Enable Docker-based tests in CI for JSON Template Layout (#2953)

Fixed

• Switch MongoDB tests to use Docker. (#2229)
• Fix reloading of the configuration from an HTTP(S) source (#2937)
• Fix putAll() in the default thread context map implementation (#2942)

Updated

• Update org.apache.logging:logging-parent to version 11.3.0

2.24.0

The 2.24.0 version of Log4j API has been enhanced with changes from the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core releases. The changes include:

• A faster default ThreadContextMap.
• Enhanced GraalVM support: native binaries that use Log4j API will no longer require additional GraalVM configuration.
• The configuration properties subsystem now only accepts the official pre-2.10 property names and the normalized post-2.10 names. Check your configuration for typos.

... (truncated)

Commits

• 4aa5efe Update the project.build.outputTimestamp property
• ab499ee Prepare release notes for 2.24.3
• 1c6ccb2 Add missing changelog entry
• 551652a Synchronize JeroMqAppender test methods
• 8ee4237 Fix assertions in LoggerMessageFactoryCustomizationTest
• 18a1deb Hardens PropertiesUtil against recursive property sources (#3263)
• bad8b56 Fix ConcurrentModificationException in updateLoggers()
• 11a3fc3 Prepare next release cycle
• e65538d Update the project.build.outputTimestamp property
• ae1137b Prepare release notes for version 2.24.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[robertlazarski]

@veithen do you still have concerns with updating log4j to the latest? If I don't hear from you in about a week, I will proceed.

[veithen]

@veithen do you still have concerns with updating log4j to the latest? If I don't hear from you in about a week, I will proceed.

The update causes build failures. If you know how to fix them, please proceed with the update.

[robertlazarski]

@veithen I added <_bundleannotations/> to the pom.xml and that seems to fix the build issues related to the Eclipse plugins. If you are aware of side effects to that fix, or still have concerns, let me know.

[robertlazarski]

@dependabot rebase

[dependabot]

Looks like org.apache.logging.log4j:log4j-bom is up-to-date now, so this is no longer needed.