+1 Using: `mvn clean verify` Env: Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec Java version: 17.0.19, vendor: Homebrew, runtime: /opt/homebrew/Cellar/openjdk@17/17.0.19/libexec/openjdk.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "26.5.1", arch: "aarch64", family: "mac"
Using: mvn verify -Prelease artifact:compare -D'reference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1327' Fails for me but this is not a release requirement. [INFO] --- artifact:3.6.0:compare (default-cli) @ log4j-bom --- [INFO] <project.build.outputTimestamp> property (= 2026-06-29T07:01:45Z) is inherited, you can override in pom.xml Downloading from reference: https://repository.apache.org/content/repositories/orgapachelogging-1327/org/apache/logging/log4j/log4j-bom/2.26.1/log4j-bom-2.26.1.buildinfo [INFO] Reference buildinfo file not found: it will be generated from downloaded reference artifacts Downloading from reference: https://repository.apache.org/content/repositories/orgapachelogging-1327/org/apache/logging/log4j/log4j-bom/2.26.1/log4j-bom-2.26.1.pom Downloaded from reference: https://repository.apache.org/content/repositories/orgapachelogging-1327/org/apache/logging/log4j/log4j-bom/2.26.1/log4j-bom-2.26.1.pom (12 kB at 75 kB/s) Downloading from reference: https://repository.apache.org/content/repositories/orgapachelogging-1327/org/apache/logging/log4j/log4j-bom/2.26.1/log4j-bom-2.26.1-cyclonedx.xml Downloaded from reference: https://repository.apache.org/content/repositories/orgapachelogging-1327/org/apache/logging/log4j/log4j-bom/2.26.1/log4j-bom-2.26.1-cyclonedx.xml (435 kB at 566 kB/s) [INFO] Minimal buildinfo generated from downloaded artifacts: /Users/garygregory/rc/log4j/target/reference/log4j-bom-2.26.1.buildinfo [ERROR] sha512 mismatch log4j-bom-2.26.1-cyclonedx.xml: investigate with diffoscope target/reference/org.apache.logging.log4j/log4j-bom-2.26.1-cyclonedx.xml target/bom.xml [ERROR] Reproducible Build output summary: 1 files ok, 1 different [ERROR] see diff target/reference/log4j-bom-2.26.1.buildinfo target/log4j-bom-2.26.1.buildinfo [ERROR] see also https://maven.apache.org/guides/mini/guide-reproducible-builds.html Gary On Mon, Jun 29, 2026 at 7:39 AM Ramanathan Muthu <[email protected]> wrote: > > This is a vote to release Apache Log4j 2.26.1. > > Website: https://logging.staged.apache.org/log4j/2.26.1/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: dd0f9d255e24e6bcc13bd2641407a409c0524803 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.1 > Nexus: > https://repository.apache.org:443/content/repositories/orgapachelogging-1327 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > Review kit: > https://logging.apache.org/logging-parent/release-review-instructions.html > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 72 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > == Release Notes > > This patch release delivers certain fixes on top of 2.26.0. > > === Fixed > > * Improve logging for LinkageError scenarios involving the > LMAX Disruptor library (#2250, #4124) > * Fix createOnDemand behavior of RollingFileAppender (#2006, #4072) > * Improve documentation for locale handling in Pattern Layout > date pattern converter (#4129, #4130) > * Fix handling of non-finite numbers encoding MapMessage to JSON (#4163) > * Fix encoding of MSGID and SD-ID fields of StructuredDataMessage > to XML (#4136) > * Fix stack trace rendering for exceptions with identity malfunction > (#3933, #4133) > * Fix resource leaks in ConfigurationSource when loading > configuration via URL fails (#4127) > * Fix KafkaAppender reporting error to error handler after > successful retry (#4125)
