dependabot[bot] opened a new pull request, #321: URL: https://github.com/apache/logging-log4j-samples/pull/321
Bumps the all group with 1 update in the /log4j-samples-graalvm directory: [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2). Updates `org.apache.logging.log4j:log4j-bom` from 2.25.0-SNAPSHOT to 3.0.0-beta3 <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-beta3</h2> <p>This release terminates the modularization process of Log4j Core, by moving all the code that uses optional <code>log4j-core</code> dependencies into new modules:</p> <ul> <li>Support for the JAnsi library has been removed since recent Windows OSes support ANSI escape sequences. See <a href="https://logging.apache.org/log4j/3.x/manual/pattern-layout.html#ansi-windows";>ANSI styling on Windows</a> for more details.</li> <li>The <a href="https://logging.apache.org/log4j/3.x/manual/appenders/delegating.html#DisruptorBlockingQueueFactory";><code>DisruptorBlockinQueue</code> queue factory</a> has been moved to a new <a href="https://logging.apache.org/log4j/3.x/components.html#log4j-conversant";><code>log4j-conversant</code> artifact</a>.</li> <li>Support for <a href="https://logging.apache.org/log4j/3.x/manual/appenders/rolling-file.html#RolloverStrategy-compress";>advanced compression algorithms</a> has been moved to a new <a href="https://logging.apache.org/log4j/3.x/components.html#log4j-compress";><code>log4j-compress</code> artifact</a>. The Gzip and Zip formats are still supported out-of-the-box.</li> </ul> <h3>Separate lifecycle</h3> <ul> <li>The <a href="https://logging.apache.org/log4j/3.x/manual/appenders/message-queue.html#FlumeAppender";>Flume Appender</a> releases will follow their own lifecycle.</li> <li>All the <a href="https://logging.apache.org/log4j/3.x/manual/installation.html#impl-core-bridges";>logging bridges</a> from and to Log4j API have been removed from the Log4j Core 3.x release. Please manage your dependencies with <a href="https://logging.apache.org/log4j/3.x/components.html#log4j-bom";><code>log4j-bom</code></a> to always use the compatible version of the logging bridges.</li> </ul> <h3>Added</h3> <ul> <li>Add <code>useFqdn</code> configuration attribute to RFC5424 Layout. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1740";>#1740</a>)</li> <li>Split off JNDI support of <code>log4j-jdbc</code> to a new <code>log4j-jdbc-jndi</code> module (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1914";>#1914</a>)</li> <li>Add <em>"Plugin Reference"</em> to the website. It is a Javadoc-on-steroids focusing on Log4j plugins. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1954";>#1954</a>)</li> <li>Split extended compression algorithm support to new <code>log4j-compress</code> module. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2921";>#2921</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Remove JAnsi library support, since Windows console supports ANSI escapes now. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/1736";>#1736</a>)</li> <li>Move <code>DisruptorBlockingQueue</code> plugin to new <code>log4j-conversant</code> module. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2914";>#2914</a>)</li> <li>Rewrite <code>JAnsiTextRenderer</code> to work without JAnsi library. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2916";>#2916</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>Switch MongoDB tests to use Docker. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2229";>#2229</a>)</li> <li>Fix custom thread-context data provider handling in lookups and filters. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2331";>#2331</a>)</li> <li>Fix reloading of the configuration from an HTTP(S) source (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2937";>#2937</a>)</li> <li>Fix Android-related issues in Log4j Core. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/3056";>#3056</a>)</li> <li>Website is migrated to Antora with several formatting and link fixes (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2443";>#2443</a>)</li> </ul> <h3>Removed</h3> <ul> <li>Remove <em>named</em> date & time formatting patterns in Pattern Layout, except for <code>UNIX</code> and <code>UNIX_MILLIS</code> (<a href="https://redirect.github.com/apache/logging-log4j2/issues/3150";>#3150</a>)</li> <li>Move Flume Appender to its own release lifecycle. (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2902";>#2902</a>)</li> <li>Remove <code>ThrowableProxy</code> and its usages (<a href="https://redirect.github.com/apache/logging-log4j2/issues/3047";>#3047</a>)</li> <li>Remove logging bridges from distribution and reference their 2.x equivalents in <code>log4j-bom</code>.</li> <li>Remove CLI tools to generate logger wrappers and convert configuration files. These tools will be available in the next release of <a href="https://logging.apache.org/log4j/transform/index.html";>Log4j Transform</a>.</li> <li>Remove deprecated <code>org.apache.logging.log4j.core.appender.rolling.action.Duration</code> class.</li> <li>Remove <code>log4j-1.2-api</code> module (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2621";>#2621</a>)</li> <li>Remove <code>log4j-iostreams</code> module (<a href="https://redirect.github.com/apache/logging-log4j2/issues/2630";>#2630</a>)</li> </ul> <h3>Updated</h3> <!-- 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-beta3";>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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </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: robots-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
