logging-log4j-kotlin
logging-log4j-kotlin copied to clipboard
Bump org.apache.logging.log4j:log4j-bom from 2.24.3 to 2.25.2
Bumps org.apache.logging.log4j:log4j-bom from 2.24.3 to 2.25.2.
Release notes
Sourced from org.apache.logging.log4j:log4j-bom's releases.
2.25.2
This patch release addresses certain minor issues detailed in the changelog.
Fixed
- Fix potential memory leak involving
LogBuilderin Log4j API to Logback bridge (#3819, #3824)- Prevent unnecessary warnings in
AbstractDriverManagerConnectionSource(#3828, #3831)- Fix missing newlines in default logging configuration for
log4j-core(#3835, #3851)- Fix missing default
Targetvalue in Console Appender (#3852)- Discard the sub-second part while obtaining the initial time (i.e., creation time) of a file in
RollingFileManager(#3068, #3872)- Fix Pattern Layout exception stack trace converters to no longer prepend newlines based on context (#3873, #3919)
- Fix the
com.google.errorprone:error_prone_annotationsdependency whose version property gets erased due to flattening (#3779, #3785, #3822, #3905)- Fix detection of
Throwableconverters inside nested Pattern Layout patterns when applyingalwaysWriteExceptions(#3920)- Fix parsing and merging of literals in
InstantPatternDynamicFormatter(#3930, #3932)2.25.1
This patch release addresses a dozen bugs in version
2.25.0, in particular:
- Resolves a concurrency issue in the new unified datetime formatter.
- Fixes build failures affecting Gradle users.
- Restores backward compatibility with Spring Boot’s common logging configuration.
- Improves handling of edge cases in GraalVM support.
Fixed
- Fix detection of the Disruptor major version in environments with non-standard thread context classloader. (#3706)
- Downgrade
spotbugs-annotationsto resolve Gradle build failures. (#3754)- Fix incorrect version resolution of
jspecifyanderror_prone_annotationsdependencies in published POM files. (#3758, #3779)- Restore compatibility with Spring Boot by allowing reconfiguration using the
LoggerContext.startmethod. (#3770)- Allow omission of the
-Alog4j.graalvm.groupIdand-Alog4j.graalvm.artifactIdarguments when building Log4j plugins. (#3771)- Broaden the OSGi manifest's
Import-Packageconstraints to support Jakarta Servlet API up to version 6. (#3787)- Enable the
resource:protocol for configuration files by default when running on GraalVM. (#3790)- Fix timestamp formatting concurrency issue, when
log4j2.enabledThreadlocalsistrue. (#3792)- Fix GraalVM reachability metadata generation for methods with annotated array type parameters, such as
@Nullable String[]. (#3796)- Resolve
PropertiesConfigurationcompatibility issues with GraalVM and address additional minor reflection-related problems. (#3800)2.25.0
This minor release introduces bug fixes, behavior improvements, and complete support for GraalVM native image generation.
GraalVM Reachability Metadata
Log4j Core and all extension modules now include embedded
GraalVM reachability metadata,
enabling seamless generation of native images with GraalVM out of the box—no manual configuration required.
For more information, refer to our GraalVM guide.[!NOTE]
When building third-party Log4j plugins, using the newGraalVmProcessor
introduced in version2.25.0will automatically generate the required reachability metadata for GraalVM native images.
However, the processor will fail the build if the requiredlog4j.graalvm.groupIdandlog4j.graalvm.artifactIdparameters are not provided.
... (truncated)
Commits
6923bd9Release changelog for version2.25.24822edeUpdate theproject.build.outputTimestampproperty380b9f2Prepare the changelog63e1812Fix parsing and merging of literals inInstantPatternDynamicFormatter(#3932)94fc126Recognize nested converters inalwaysWriteExceptions(#3920)427fa60doc: clarify%exwhitespace behavior across versions (#3918)4ed5a1efix: make%exbehavior context-independent (#3919)7268f03Update theproject.build.outputTimestampproperty5a71c91Prepare the changelog3a57060DefaultLayout: Append a newline to the serialized LogEvent (#3851)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.