dependabot[bot] opened a new pull request, #173: URL: https://github.com/apache/logging-log4j-samples/pull/173
Bumps [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2) from 2.24.0-SNAPSHOT to 3.0.0-beta2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/apache/logging-log4j2/releases";>org.apache.logging.log4j:log4j-bom's releases</a>.</em></p> <blockquote> <h2>3.0.0-beta2</h2> <p>This release provides a continuation of the modularization process of Log4j Core.</p> <p>The following features were moved to separate artifacts:</p> <ul> <li>The async logger feature was moved to <code>log4j-async-logger</code> and it was upgraded to use LMAX Disruptor 4.x. The async appender is still available by default in <code>log4j-core</code>.</li> <li>The YAML configuration is available now in <code>log4j-config-yaml</code>.</li> <li>The Java properties configuration was removed and replaced with a similar format based on <code>jackson-dataformat-properties</code> in a new <code>log4j-config-properties</code> artifact.</li> </ul> <p>Other features were removed:</p> <ul> <li>Jetty 9.x users are encouraged to migrate to Jetty 10.x or later and replace <code>log4j-appserver</code> with <code>log4j-slf4j2-impl</code>.</li> <li>Tomcat JULI support will be available from a third-party (cf. <a href="https://github.com/copernik-eu/log4j-plugins";>copernik-eu/log4j-plugins</a>).</li> <li>Apache Commons Logging users are encouraged to upgrade <code>commons-logging</code> to version 1.3.0 or later and remove <code>log4j-jcl</code>.</li> <li>Support for the XML layout was dropped.</li> <li>Support for JMX was dropped and will be replaced with a more recenttechnology.</li> </ul> <h3>Added</h3> <ul> <li>Add and update DSLs for setting up dependency injection for test and non-test code. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2147";>#2147</a>)</li> <li>Add a <code>ConfigurationExtension</code> mechanism to allow third-party JARs to extend the <code><Configuration></code> element.</li> <li>Add a new properties configuration factory based on <code>jackson-dataformat-properties</code>.</li> </ul> <h3>Changed</h3> <ul> <li>Change the order of evaluation of <code>FormattedMessage</code> formatters. Messages are evaluated using <code>java.util.Format</code> only if they don't comply to the <code>java.text.MessageFormat</code> or <code>ParameterizedMessage</code> format. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1223";>#1223</a>)</li> <li>Split off async logger support into a new <code>log4j-async-logger</code> module.</li> <li>Split off YAML configuration into a new <code>log4j-config-yaml</code> module.</li> </ul> <h3>Fixed</h3> <ul> <li>Rewrote message parameter formatter with improved escape handling (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1626";>#1626</a>)</li> <li>The MongoDb4 appender now supports long values to configure <code>collectionSize</code> (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1747";>#1747</a>)</li> <li>Mark <code>JdkMapAdapterStringMap</code> as frozen if map is immutable. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2098";>#2098</a>)</li> <li>Fix regression in <code>JdkMapAdapterStringMap</code> performance. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2238";>#2238</a>)</li> <li>Prevents ClassCastException when trying to assign a SimpleLoggerContext to a core LoggerContext (LOG4J2-1921)</li> <li>Possible NullPointerException in MongoDb4DocumentObject, MongoDbDocumentObject, DefaultNoSqlObject. (LOG4J2-3392)</li> <li>Fix NPE in <code>CloseableThreadContext</code>. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1426";>#1426</a>)</li> <li>Fix NPE in <code>RollingFileManager</code>. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1645";>#1645</a>)</li> <li>Fix <code>log4j-spring-cloud-config-client</code> dependencies to include only those required. (2157)</li> <li>Workaround a Coursier/Ivy dependency resolution bug affecting <code>log4j-slf4j-impl</code> and <code>log4j-mongodb3</code>. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2065";>#2065</a>)</li> </ul> <h3>Removed</h3> <ul> <li>Removed legacy <code>2.x</code> properties configuration factory.</li> <li>Removed <code>DefaultLogEventFactory</code></li> <li>Removed <code>log4j-appserver</code> module (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2257";>#2257</a>)</li> <li>Removed <code>org.apache.logging.log4j.core.parser</code> and related packages. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2154";>#2154</a>)</li> <li>Removed <code>log4j-jcl</code> module (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2257";>#2257</a>)</li> <li>Removed JMX support.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/apache/logging-log4j2/commits/rel/3.0.0-beta2";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
