You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@yazi.ci> on 2026/05/04 07:45:47 UTC

[VOTE] Release Apache Log4j `2.26.0`

This is a vote to release the Apache Log4j `2.26.0`.

Website: https://logging.staged.apache.org/log4j/2.26.0
GitHub: https://github.com/apache/logging-log4j2
Commit: c1ad2a66cc90e643ec319b9e131764c9710bebc5
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.0
Nexus: https://repository.apache.org:443/content/repositories/orgapachelogging-1325
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 minor release delivers all the fixes in the `[2.25.0, 2.25.4]`
version range, plus some new fixes, and several other
improvements and features.

=== Added

* Add a new `ConfigurationFactory::getConfiguration` method
  accepting multiple `URI`s (#3775, #3921)
* Add and export
  `org.apache.logging.log4j.core.pattern.NamedInstantPattern`
  enabling users to programmatically access named date
  & time patterns supported by Pattern Layout (#3789)
* Add `log4j.plugin.processor.minAllowedMessageKind`
  annotation processor option to `PluginProcessor` to filter
  diagnostic messages by severity. This allows builds that
  treat compiler notes as errors (e.g. Maven with `-Werror`)
  to suppress informational notes emitted during normal
  plugin processing. (#3380, #4063)
* Add missing setters to `Rfc5424LayoutBuilder`

=== Changed

* Ensure scripts in the global `Scripts` element have
  explicit names by throwing a `ConfigurationException`
  for unnamed ones. (#3176)
* Simplify file manager registry factory methods (#3968)

=== Deprecated

* Deprecated withers in builder classes in favor of setters.
  This change improves API consistency with Log4j Core
  3 and helps users adapt to the upcoming changes. (#3750)

=== Fixed

* Fix script resolution failure when the `Scripts` element
  is placed after a `ScriptRef` in the configuration. (#3336)
* Fix `ArrayIndexOutOfBoundsException` thrown by
  `ThrowableStackTraceRenderer` when the stack trace
  is modified concurrently (#3940, #3955)
* Fix `SLF4JLogger.atFatal()` returning `atLevel(Level.TRACE)`
  instead of `atLevel(Level.FATAL)`. This was causing
  `FATAL`-level log events to be silently discarded when using
  the fluent API through the `log4j-to-slf4j` bridge. (#4068, #4089)
* Fix Javadoc references across module boundaries
  (i.e., cross-references) (#4099, #4100)
* Fix header write in `RollingRandomAccessFileManager` that
  was being incorrectly skipped if `append=true` and the file
  didn't exist before
* Fix a properties file configuration regression caused by not
  referenced loggers, appenders, and filters (#4036, #4069)

=== Removed

* Remove the `jvmrunargs` lookup. (#3874)

=== Updated

* Update `org.junit:junit-bom` to version `5.13.4` (#3850)
* Update `org.mongodb:bson` to version `5.6.1` (#3961)
* Update `org.xerial.snappy:snappy-java` to version `1.1.10.8` (#3841)

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Jan Friedrich <fr...@apache.org>.
+1 (binding)

Confirmed the release on my Linux system by following the steps provided 
in the review kit.

openjdk 17.0.18 2026-01-20
OpenJDK Runtime Environment (build 17.0.18+8-Ubuntu-124.04.1)
OpenJDK 64-Bit Server VM (build 17.0.18+8-Ubuntu-124.04.1, mixed mode, 
sharing)

Jan

On 5/4/26 09:45, Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j `2.26.0`.
> 
> Website: https://logging.staged.apache.org/log4j/2.26.0
> GitHub: https://github.com/apache/logging-log4j2
> Commit: c1ad2a66cc90e643ec319b9e131764c9710bebc5
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.0
> Nexus: https://repository.apache.org:443/content/repositories/orgapachelogging-1325
> 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 minor release delivers all the fixes in the `[2.25.0, 2.25.4]`
> version range, plus some new fixes, and several other
> improvements and features.
> 
> === Added
> 
> * Add a new `ConfigurationFactory::getConfiguration` method
>    accepting multiple `URI`s (#3775, #3921)
> * Add and export
>    `org.apache.logging.log4j.core.pattern.NamedInstantPattern`
>    enabling users to programmatically access named date
>    & time patterns supported by Pattern Layout (#3789)
> * Add `log4j.plugin.processor.minAllowedMessageKind`
>    annotation processor option to `PluginProcessor` to filter
>    diagnostic messages by severity. This allows builds that
>    treat compiler notes as errors (e.g. Maven with `-Werror`)
>    to suppress informational notes emitted during normal
>    plugin processing. (#3380, #4063)
> * Add missing setters to `Rfc5424LayoutBuilder`
> 
> === Changed
> 
> * Ensure scripts in the global `Scripts` element have
>    explicit names by throwing a `ConfigurationException`
>    for unnamed ones. (#3176)
> * Simplify file manager registry factory methods (#3968)
> 
> === Deprecated
> 
> * Deprecated withers in builder classes in favor of setters.
>    This change improves API consistency with Log4j Core
>    3 and helps users adapt to the upcoming changes. (#3750)
> 
> === Fixed
> 
> * Fix script resolution failure when the `Scripts` element
>    is placed after a `ScriptRef` in the configuration. (#3336)
> * Fix `ArrayIndexOutOfBoundsException` thrown by
>    `ThrowableStackTraceRenderer` when the stack trace
>    is modified concurrently (#3940, #3955)
> * Fix `SLF4JLogger.atFatal()` returning `atLevel(Level.TRACE)`
>    instead of `atLevel(Level.FATAL)`. This was causing
>    `FATAL`-level log events to be silently discarded when using
>    the fluent API through the `log4j-to-slf4j` bridge. (#4068, #4089)
> * Fix Javadoc references across module boundaries
>    (i.e., cross-references) (#4099, #4100)
> * Fix header write in `RollingRandomAccessFileManager` that
>    was being incorrectly skipped if `append=true` and the file
>    didn't exist before
> * Fix a properties file configuration regression caused by not
>    referenced loggers, appenders, and filters (#4036, #4069)
> 
> === Removed
> 
> * Remove the `jvmrunargs` lookup. (#3874)
> 
> === Updated
> 
> * Update `org.junit:junit-bom` to version `5.13.4` (#3850)
> * Update `org.mongodb:bson` to version `5.6.1` (#3961)
> * Update `org.xerial.snappy:snappy-java` to version `1.1.10.8` (#3841)


Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
OK, after updating Java 8 to it works: +1.

Using "mvn clean verify"

java version "1.8.0_481"
Java(TM) SE Runtime Environment (build 1.8.0_481-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.481-b10, mixed mode)

Openjdk version "17.0.19" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)

Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"

Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64

Docker version 29.4.1, build 055a478

Gary

On Tue, May 5, 2026 at 5:38 PM Gary Gregory <ga...@gmail.com> wrote:
>
> On Tue, May 5, 2026 at 5:30 PM Gary Gregory <ga...@gmail.com> wrote:
> >
> > On Tue, May 5, 2026 at 5:11 PM Piotr P. Karwasz
> > <pi...@mailing.copernik.eu> wrote:
> > >
> > > Hi Gary,
> > >
> > > On 5.05.2026 13:14, Gary Gregory wrote:
> > > > Thank you for the update Piotr. So don't you need to enable the
> > > > "docker" profile? I don't see "-P docker" above.
> > >
> > > You can enable the profile explicitly, but it is activated by default
> > > when `CI=true`. Admittedly, picking a less implicit trigger would have
> > > been a better choice.
> > >
> > > On 5.05.2026 13:26, Gary Gregory wrote:
> > > >   Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c
> > > > [localized]]
> > >
> > > You've hit a JDK 8 bug:
> > >
> > > https://bugs.openjdk.org/browse/JDK-8252489
> >
> > But I'm using Java 17:
> >
> > java -version
> > openjdk version "17.0.19" 2026-04-21
> > OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
> > OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)
> >
> > The build doesn't run at all on Java 8:
> >
> > CI=true mvn clean verify \
> >     -P docker \
> >     -Ddocker-maven-plugin.version=0.48.1
> > Unrecognized option: --add-exports
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> >
> > java -version
> > java version "1.8.0_471"
> > Java(TM) SE Runtime Environment (build 1.8.0_471-b09)
> > Java HotSpot(TM) 64-Bit Server VM (build 25.471-b09, mixed mode)
>
> I'll update my Java 8...
>
> Gary
>
> >
> > Gary
> >
> >
> > >
> > > The format that `Throwable#printStackTrace()` produces for circular
> > > references changed in *8u272*: both the `Caused by:` / `Suppressed:`
> > > caption and the space after `[CIRCULAR REFERENCE:` were added by that fix.
> > >
> > > Our test compares Log4j's output to the live JVM's `printStackTrace()`
> > > output, so it only passes on 8u272 or newer. My local JDK is 1.8.0_482,
> > > which is why it passes for me; you must be running an older 8u build.
> > >
> > > Piotr

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
On Tue, May 5, 2026 at 5:30 PM Gary Gregory <ga...@gmail.com> wrote:
>
> On Tue, May 5, 2026 at 5:11 PM Piotr P. Karwasz
> <pi...@mailing.copernik.eu> wrote:
> >
> > Hi Gary,
> >
> > On 5.05.2026 13:14, Gary Gregory wrote:
> > > Thank you for the update Piotr. So don't you need to enable the
> > > "docker" profile? I don't see "-P docker" above.
> >
> > You can enable the profile explicitly, but it is activated by default
> > when `CI=true`. Admittedly, picking a less implicit trigger would have
> > been a better choice.
> >
> > On 5.05.2026 13:26, Gary Gregory wrote:
> > >   Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c
> > > [localized]]
> >
> > You've hit a JDK 8 bug:
> >
> > https://bugs.openjdk.org/browse/JDK-8252489
>
> But I'm using Java 17:
>
> java -version
> openjdk version "17.0.19" 2026-04-21
> OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)
>
> The build doesn't run at all on Java 8:
>
> CI=true mvn clean verify \
>     -P docker \
>     -Ddocker-maven-plugin.version=0.48.1
> Unrecognized option: --add-exports
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> java -version
> java version "1.8.0_471"
> Java(TM) SE Runtime Environment (build 1.8.0_471-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.471-b09, mixed mode)

I'll update my Java 8...

Gary

>
> Gary
>
>
> >
> > The format that `Throwable#printStackTrace()` produces for circular
> > references changed in *8u272*: both the `Caused by:` / `Suppressed:`
> > caption and the space after `[CIRCULAR REFERENCE:` were added by that fix.
> >
> > Our test compares Log4j's output to the live JVM's `printStackTrace()`
> > output, so it only passes on 8u272 or newer. My local JDK is 1.8.0_482,
> > which is why it passes for me; you must be running an older 8u build.
> >
> > Piotr

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Gary,

On 5.05.2026 23:30, Gary Gregory wrote:
> But I'm using Java 17:
> 
> java -version
> openjdk version "17.0.19" 2026-04-21
> OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)
> 
> The build doesn't run at all on Java 8:
> 
> CI=true mvn clean verify \
>     -P docker \
>     -Ddocker-maven-plugin.version=0.48.1
> Unrecognized option: --add-exports
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> 
> java -version
> java version "1.8.0_471"
> Java(TM) SE Runtime Environment (build 1.8.0_471-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.471-b09, mixed mode)


When CI=true, the Surefire plugin uses Maven Toolchains to run the tests
using JDK 8. Can you check in your ~/.m2/toolchains.xml file, which JDK
8 version do you have configured there?

Piotr

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
On Tue, May 5, 2026 at 5:11 PM Piotr P. Karwasz
<pi...@mailing.copernik.eu> wrote:
>
> Hi Gary,
>
> On 5.05.2026 13:14, Gary Gregory wrote:
> > Thank you for the update Piotr. So don't you need to enable the
> > "docker" profile? I don't see "-P docker" above.
>
> You can enable the profile explicitly, but it is activated by default
> when `CI=true`. Admittedly, picking a less implicit trigger would have
> been a better choice.
>
> On 5.05.2026 13:26, Gary Gregory wrote:
> >   Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c
> > [localized]]
>
> You've hit a JDK 8 bug:
>
> https://bugs.openjdk.org/browse/JDK-8252489

But I'm using Java 17:

java -version
openjdk version "17.0.19" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)

The build doesn't run at all on Java 8:

CI=true mvn clean verify \
    -P docker \
    -Ddocker-maven-plugin.version=0.48.1
Unrecognized option: --add-exports
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

java -version
java version "1.8.0_471"
Java(TM) SE Runtime Environment (build 1.8.0_471-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.471-b09, mixed mode)

Gary


>
> The format that `Throwable#printStackTrace()` produces for circular
> references changed in *8u272*: both the `Caused by:` / `Suppressed:`
> caption and the space after `[CIRCULAR REFERENCE:` were added by that fix.
>
> Our test compares Log4j's output to the live JVM's `printStackTrace()`
> output, so it only passes on 8u272 or newer. My local JDK is 1.8.0_482,
> which is why it passes for me; you must be running an older 8u build.
>
> Piotr

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Gary,

On 5.05.2026 13:14, Gary Gregory wrote:
> Thank you for the update Piotr. So don't you need to enable the
> "docker" profile? I don't see "-P docker" above.

You can enable the profile explicitly, but it is activated by default
when `CI=true`. Admittedly, picking a less implicit trigger would have
been a better choice.

On 5.05.2026 13:26, Gary Gregory wrote:
>   Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c
> [localized]]

You've hit a JDK 8 bug:

https://bugs.openjdk.org/browse/JDK-8252489

The format that `Throwable#printStackTrace()` produces for circular
references changed in *8u272*: both the `Caused by:` / `Suppressed:`
caption and the space after `[CIRCULAR REFERENCE:` were added by that fix.

Our test compares Log4j's output to the live JVM's `printStackTrace()`
output, so it only passes on 8u272 or newer. My local JDK is 1.8.0_482,
which is why it passes for me; you must be running an older 8u build.

Piotr

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
If I run:

  CI=true mvn clean verify \
    -P docker \
    -Prelease \
    -Ddocker-maven-plugin.version=0.48.1 \
    -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325

I get:

...
  Caused by: foo.TestFriendlyException: r [localized]
  at java.net.Socket.<init>(Socket.java:228)
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.<clinit>(TestFriendlyException.java:83)
  at bar.OrgApacheReplacement.someMethod(OrgApacheReplacement.java:0)
  Suppressed: foo.TestFriendlyException: r_s [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:96)
  ... 2 more
  Suppressed: foo.TestFriendlyException: r_s_s [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:96)
  ... 3 more
  Caused by: foo.TestFriendlyException: r_s_c [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:93)
  ... 3 more
  Caused by: foo.TestFriendlyException: r_c [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:93)
  ... 2 more
  Suppressed: foo.TestFriendlyException: r_c_s [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:96)
  ... 3 more
  Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c [localized]]
  Caused by: foo.TestFriendlyException: r_c_c [localized]
  at foo.TestFriendlyException.create(TestFriendlyException.java:91)
  at foo.TestFriendlyException.create(TestFriendlyException.java:93)
  ... 3 more
  Caused by: [CIRCULAR REFERENCE: foo.TestFriendlyException: r_c [localized]]
  "
[INFO]
[INFO]
[ERROR] Tests run: 8655, Failures: 7, Errors: 0, Skipped: 36

See https://gist.github.com/garydgregory/fd77dab2e067301b8c05f43ad974f290

Using:

openjdk version "17.0.19" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)

Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"

Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64

Docker version 29.4.1, build 055a478

Gary

On Tue, May 5, 2026 at 7:14 AM Gary Gregory <ga...@gmail.com> wrote:
>
> On Mon, May 4, 2026 at 4:50 PM Piotr P. Karwasz
> <pi...@mailing.copernik.eu> wrote:
> >
> > Hi Gary,
> >
> > On 4.05.2026 20:55, Gary Gregory wrote:
> > > Since build reproducibility is broken and not a requirement, it should
> > > be marked as optional in the review kit.
> >
> >
> > Reproducibility isn't broken: I reproduced the artifacts successfully.
> > There's just a temporary requirement (`CI=true`) that isn't in the
> > review kit and that Volkan forgot to mention in the vote email. I
> > described it in an answer to your previous build attempt [1].
> >
> > > I am going to ignore it and use a more simple "mvn clean verify -P
> > docker" check.
> > > This gives me:
> > >
> > > [ERROR] Errors:
> > > [ERROR]   RollingAppenderDirectCronTest.testAppender:57 [...]
> >
> >
> > Those tests have been flaky for a long time, which is why our CI runs go
> > through Develocity for flakiness tracking. `git blame` suggests they've
> > been with us roughly since the dawn of `RollingAppenderDirectCronTest`
> > itself, so they predate any of our recent releases. Fixing them is on
> > the wish list: volunteers very welcome!
> >
> > On 4.05.2026 21:01, Gary Gregory wrote:
> > > For fun, I restarted the build and got a different error:
> > > [...]
> > > [ERROR] Failed to execute goal
> > io.fabric8:docker-maven-plugin:0.46.0:start [...]
> >
> >
> > That's the Docker API incompatibility I ran into during verification
> > (and mentioned in my +1 vote [2]). It looks like it was introduced in
> > Docker API 1.44; our CI runs on an older version, so it slipped past us.
> >
> > You've motivated me to actually try running the Docker tests though, so
> > thanks for that. The following works for me:
> >
> >     CI=true ./mvnw verify artifact:compare \
> >       -Prelease \
> >       -Ddocker-maven-plugin.version=0.48.1 \
> >
> > -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325
> >
>
> Thank you for the update Piotr. So do you don't you need to enable the
> "docker" profile? I don't see "-P docker" above.
>
> Gary
>
> > Piotr
> >
> > [1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj
> > [2] https://lists.apache.org/thread/thy4tpblpq01fd7ftv75h7pwo0l9brtw

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
On Mon, May 4, 2026 at 4:50 PM Piotr P. Karwasz
<pi...@mailing.copernik.eu> wrote:
>
> Hi Gary,
>
> On 4.05.2026 20:55, Gary Gregory wrote:
> > Since build reproducibility is broken and not a requirement, it should
> > be marked as optional in the review kit.
>
>
> Reproducibility isn't broken: I reproduced the artifacts successfully.
> There's just a temporary requirement (`CI=true`) that isn't in the
> review kit and that Volkan forgot to mention in the vote email. I
> described it in an answer to your previous build attempt [1].
>
> > I am going to ignore it and use a more simple "mvn clean verify -P
> docker" check.
> > This gives me:
> >
> > [ERROR] Errors:
> > [ERROR]   RollingAppenderDirectCronTest.testAppender:57 [...]
>
>
> Those tests have been flaky for a long time, which is why our CI runs go
> through Develocity for flakiness tracking. `git blame` suggests they've
> been with us roughly since the dawn of `RollingAppenderDirectCronTest`
> itself, so they predate any of our recent releases. Fixing them is on
> the wish list: volunteers very welcome!
>
> On 4.05.2026 21:01, Gary Gregory wrote:
> > For fun, I restarted the build and got a different error:
> > [...]
> > [ERROR] Failed to execute goal
> io.fabric8:docker-maven-plugin:0.46.0:start [...]
>
>
> That's the Docker API incompatibility I ran into during verification
> (and mentioned in my +1 vote [2]). It looks like it was introduced in
> Docker API 1.44; our CI runs on an older version, so it slipped past us.
>
> You've motivated me to actually try running the Docker tests though, so
> thanks for that. The following works for me:
>
>     CI=true ./mvnw verify artifact:compare \
>       -Prelease \
>       -Ddocker-maven-plugin.version=0.48.1 \
>
> -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325
>

Thank you for the update Piotr. So do you don't you need to enable the
"docker" profile? I don't see "-P docker" above.

Gary

> Piotr
>
> [1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj
> [2] https://lists.apache.org/thread/thy4tpblpq01fd7ftv75h7pwo0l9brtw

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Gary,

On 4.05.2026 20:55, Gary Gregory wrote:
> Since build reproducibility is broken and not a requirement, it should
> be marked as optional in the review kit.


Reproducibility isn't broken: I reproduced the artifacts successfully.
There's just a temporary requirement (`CI=true`) that isn't in the
review kit and that Volkan forgot to mention in the vote email. I
described it in an answer to your previous build attempt [1].

> I am going to ignore it and use a more simple "mvn clean verify -P
docker" check.
> This gives me:
>
> [ERROR] Errors:
> [ERROR]   RollingAppenderDirectCronTest.testAppender:57 [...]


Those tests have been flaky for a long time, which is why our CI runs go
through Develocity for flakiness tracking. `git blame` suggests they've
been with us roughly since the dawn of `RollingAppenderDirectCronTest`
itself, so they predate any of our recent releases. Fixing them is on
the wish list: volunteers very welcome!

On 4.05.2026 21:01, Gary Gregory wrote:
> For fun, I restarted the build and got a different error:
> [...]
> [ERROR] Failed to execute goal
io.fabric8:docker-maven-plugin:0.46.0:start [...]


That's the Docker API incompatibility I ran into during verification
(and mentioned in my +1 vote [2]). It looks like it was introduced in
Docker API 1.44; our CI runs on an older version, so it slipped past us.

You've motivated me to actually try running the Docker tests though, so
thanks for that. The following works for me:

    CI=true ./mvnw verify artifact:compare \
      -Prelease \
      -Ddocker-maven-plugin.version=0.48.1 \

-Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325

Piotr

[1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj
[2] https://lists.apache.org/thread/thy4tpblpq01fd7ftv75h7pwo0l9brtw

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
For fun, I restarted the build and got a different error:

...
Downloaded from central:
https://repo.maven.apache.org/maven2/org/bouncycastle/bcpkix-jdk15on/1.65/bcpkix-jdk15on-1.65.jar
(879 kB at 1.7 MB/s)
Downloaded from central:
https://repo.maven.apache.org/maven2/org/bouncycastle/bcprov-jdk15on/1.65/bcprov-jdk15on-1.65.jar
(4.5 MB at 7.3 MB/s)
[INFO] DOCKER> Pulling from library/elasticsearch
02184a91e435: Pull complete
2602e1c5e883: Pull complete
a998be0af0b8: Pull complete
ed15297e21ea: Pull complete
8a980f875cea: Pull complete
4f4fb700ef54: Pull complete
5424ef9d14b5: Pull complete
d00ed398ddf3: Pull complete
a13f6685425f: Pull complete
711be2f9f33b: Pull complete
3fc17721b5ae: Download complete
ab63c215921f: Download complete
[INFO] DOCKER> Digest:
sha256:c0e8efbd41e3bdc912293889bae4402f3166f8d5a642f7f4d711b58dd8c2877e
[INFO] DOCKER> Status: Downloaded newer image for elasticsearch:9.2.0
[INFO] DOCKER> Pulled elasticsearch:9.2.0 in 25 seconds
[INFO] DOCKER> Pulling from library/logstash
4f4fb700ef54: Pull complete
205b1025b115: Pull complete
4c00b3f750a1: Pull complete
bb09c2129a5c: Pull complete
c0bda2a661ef: Pull complete
16a8d65ee75e: Pull complete
ac97e6df1725: Pull complete
704cc6e755b6: Pull complete
a8a9eade8d7e: Download complete
8e79ffcf06ed: Download complete
[INFO] DOCKER> Digest:
sha256:e73333d13757fb744d45861011fec26410e1131ef4154d86e2b06092d2f0232c
[INFO] DOCKER> Status: Downloaded newer image for logstash:9.2.0
[INFO] DOCKER> Pulled logstash:9.2.0 in 21 seconds
[INFO] DOCKER> [elasticsearch:9.2.0] "elasticsearch": Start container
04415ba58e2d
[ERROR] DOCKER> Error occurred during container startup, shutting down...
[INFO] DOCKER> [elasticsearch:9.2.0] "elasticsearch": Stop and removed
container 04415ba58e2d after 0 ms
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Log4j BOM 2.26.0:
[INFO]
[INFO] Apache Log4j BOM ................................... SUCCESS [  5.259 s]
[INFO] Apache Log4j Parent ................................ SUCCESS [  0.382 s]
[INFO] Apache Log4j API Java 9 support .................... SUCCESS [  2.464 s]
[INFO] Apache Log4j API ................................... SUCCESS [  6.492 s]
[INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [  1.545 s]
[INFO] Apache Log4j Core .................................. SUCCESS [ 15.950 s]
[INFO] Apache Log4j API Tests ............................. SUCCESS [  9.856 s]
[INFO] Apache Log4j Core Tests ............................ SUCCESS [01:24 min]
[INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [ 10.891 s]
[INFO] Apache Log4j App Server Support .................... SUCCESS [  1.291 s]
[INFO] Log4j API to SLF4J Adapter ......................... SUCCESS [  2.769 s]
[INFO] SLF4J 1 Binding for Log4j API ...................... SUCCESS [  3.259 s]
[INFO] Apache Log4j Cassandra ............................. SUCCESS [  2.577 s]
[INFO] Apache Log4j fuzz tests ............................ SUCCESS [  1.528 s]
[INFO] Apache Log4j Core fuzz tests ....................... SUCCESS [  1.174 s]
[INFO] Apache Log4j Core Integration Tests ................ SUCCESS [  0.762 s]
[INFO] Apache Log4j CouchDB ............................... SUCCESS [  1.559 s]
[INFO] Apache Log4j Docker Library ........................ SUCCESS [  1.505 s]
[INFO] Apache Log4j Streaming Interface ................... SUCCESS [  4.140 s]
[INFO] Apache Log4j Jakarta JMS ........................... SUCCESS [  2.680 s]
[INFO] Apache Log4j Jakarta SMTP .......................... SUCCESS [  2.524 s]
[INFO] Apache Log4j Jakarta Web ........................... SUCCESS [  3.261 s]
[INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [  2.264 s]
[INFO] Apache Log4j JPA ................................... SUCCESS [  3.934 s]
[INFO] Apache Log4j JDK Platform Logging Adapter .......... SUCCESS [  2.224 s]
[INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [  2.544 s]
[INFO] Apache Log4j JUL Adapter ........................... SUCCESS [  5.674 s]
[INFO] Apache Log4j JSON Template Layout .................. SUCCESS [  3.377 s]
[INFO] Apache Log4j JSON Template Layout fuzz tests ....... SUCCESS [  1.260 s]
[INFO] Apache Log4j JSON Template Layout tests ............ FAILURE [ 58.502 s]
[INFO] Apache Log4j MongoDB 4 ............................. SKIPPED
[INFO] Apache Log4j MongoDB Appender ...................... SKIPPED
[INFO] Apache Log4j to JUL Bridge ......................... SKIPPED
[INFO] Apache Log4j OSGi tests ............................ SKIPPED
[INFO] Apache Log4J Performance Tests ..................... SKIPPED
[INFO] SLF4J 2 Provider for Log4j API ..................... SKIPPED
[INFO] SLF4J 2 Provider for Log4j API fuzz tests .......... SKIPPED
[INFO] Apache Log4j Spring Boot Support ................... SKIPPED
[INFO] Apache Log4j Spring Cloud Config Client Support .... SKIPPED
[INFO] Apache Log4j Web ................................... SKIPPED
[INFO] Apache Log4j Tag Library ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:06 min
[INFO] Finished at: 2026-05-04T14:59:47-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
io.fabric8:docker-maven-plugin:0.46.0:start (start) on project
log4j-layout-template-json-test: Execution start of goal
io.fabric8:docker-maven-plugin:0.46.0:start failed: Cannot invoke
"com.google.gson.JsonElement.isJsonNull()" because the return value of
"com.google.gson.JsonObject.get(String)" is null -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :log4j-layout-template-json-test

Gary

On Mon, May 4, 2026 at 2:55 PM Gary Gregory <ga...@gmail.com> wrote:
>
> Since build reproducibility is broken and not a requirement, it should
> be marked as optional in the review kit. I am going to ignore it and
> use a more simple "mvn clean verify -P docker" check. This gives me:
>
> [ERROR] Errors:
> [ERROR]   RollingAppenderDirectCronTest.testAppender:57 » Runtime
> java.lang.RuntimeException: Rollover completion verification failure
> for file: /Users/garygregory/rc/log4j-2.26.0/src/log4j-core-test/target/logs/core/appender/rolling/RollingAppenderDirectCronTest_69f8eb82_16734836558386803739/test-2026-05-04T02-54-59.log
> [INFO]
> [ERROR] Tests run: 8656, Failures: 0, Errors: 1, Skipped: 35
>
> Using:
>
> Openjdk version "17.0.19" 2026-04-21
> OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)
>
> Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
> Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"
>
> Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
> 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64
>
> Docker version 29.4.1, build 055a478
>
> Gary
>
> On Mon, May 4, 2026 at 2:19 PM Piotr P. Karwasz
> <pi...@mailing.copernik.eu> wrote:
> >
> > Hi Gary,
> >
> > On 4.05.2026 14:16, Gary Gregory wrote:
> > > I tried to adapt the review kit to my setup, running:
> > >
> > > sh mvn verify -P docker \
> > >   -Prelease artifact:compare \
> > >   -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325
> >
> >
> > Reproducibility likely requires:
> >
> >     export CI=true
> >
> > This variable toggles the activation of two profiles (`java8-tests` and
> > `java8-incompat-fixes`) that allow CI to run tests against a JDK 8
> > toolchain. Unfortunately, it also has some side effects on the generated
> > artifacts:
> >
> > - `jspecify` appears in the `test` scope instead of `provided` scope.
> > The artifact is added to the `test` scope by the profile as a workaround
> > for a JDK 8 bug, so the SBOMs generated with `CI=true` and `CI=false`
> > differ slightly in where `jspecify` appears.
> > - For reasons I couldn't fully pin down, the POM files embedded in the
> > `*-sources.jar` archive may differ by a comment. The order in which a
> > POM-modifying plugin and `maven-source-plugin` execute differs between
> > `CI=true` and `CI=false`.
> >
> > We should almost certainly fix this going forward, for example, by
> > running the `deploy-release` workflow without the JDK 8 fixups and
> > reserving those for `build` runs[*].
> >
> > Piotr
> >
> > [*] As an aside: the `build` workflow is a misnomer. Its main purpose is
> > to run unit tests, and building the artifacts is just a side effect.
> > Conversely, the main purpose of `deploy-release` is to build the
> > artifacts (without testing) and deploy them to the staging repository.
> >

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
Since build reproducibility is broken and not a requirement, it should
be marked as optional in the review kit. I am going to ignore it and
use a more simple "mvn clean verify -P docker" check. This gives me:

[ERROR] Errors:
[ERROR]   RollingAppenderDirectCronTest.testAppender:57 » Runtime
java.lang.RuntimeException: Rollover completion verification failure
for file: /Users/garygregory/rc/log4j-2.26.0/src/log4j-core-test/target/logs/core/appender/rolling/RollingAppenderDirectCronTest_69f8eb82_16734836558386803739/test-2026-05-04T02-54-59.log
[INFO]
[ERROR] Tests run: 8656, Failures: 0, Errors: 1, Skipped: 35

Using:

Openjdk version "17.0.19" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)

Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"

Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64

Docker version 29.4.1, build 055a478

Gary

On Mon, May 4, 2026 at 2:19 PM Piotr P. Karwasz
<pi...@mailing.copernik.eu> wrote:
>
> Hi Gary,
>
> On 4.05.2026 14:16, Gary Gregory wrote:
> > I tried to adapt the review kit to my setup, running:
> >
> > sh mvn verify -P docker \
> >   -Prelease artifact:compare \
> >   -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325
>
>
> Reproducibility likely requires:
>
>     export CI=true
>
> This variable toggles the activation of two profiles (`java8-tests` and
> `java8-incompat-fixes`) that allow CI to run tests against a JDK 8
> toolchain. Unfortunately, it also has some side effects on the generated
> artifacts:
>
> - `jspecify` appears in the `test` scope instead of `provided` scope.
> The artifact is added to the `test` scope by the profile as a workaround
> for a JDK 8 bug, so the SBOMs generated with `CI=true` and `CI=false`
> differ slightly in where `jspecify` appears.
> - For reasons I couldn't fully pin down, the POM files embedded in the
> `*-sources.jar` archive may differ by a comment. The order in which a
> POM-modifying plugin and `maven-source-plugin` execute differs between
> `CI=true` and `CI=false`.
>
> We should almost certainly fix this going forward, for example, by
> running the `deploy-release` workflow without the JDK 8 fixups and
> reserving those for `build` runs[*].
>
> Piotr
>
> [*] As an aside: the `build` workflow is a misnomer. Its main purpose is
> to run unit tests, and building the artifacts is just a side effect.
> Conversely, the main purpose of `deploy-release` is to build the
> artifacts (without testing) and deploy them to the staging repository.
>

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Gary,

On 4.05.2026 14:16, Gary Gregory wrote:
> I tried to adapt the review kit to my setup, running:
> 
> sh mvn verify -P docker \
>   -Prelease artifact:compare \
>   -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325


Reproducibility likely requires:

    export CI=true

This variable toggles the activation of two profiles (`java8-tests` and
`java8-incompat-fixes`) that allow CI to run tests against a JDK 8
toolchain. Unfortunately, it also has some side effects on the generated
artifacts:

- `jspecify` appears in the `test` scope instead of `provided` scope.
The artifact is added to the `test` scope by the profile as a workaround
for a JDK 8 bug, so the SBOMs generated with `CI=true` and `CI=false`
differ slightly in where `jspecify` appears.
- For reasons I couldn't fully pin down, the POM files embedded in the
`*-sources.jar` archive may differ by a comment. The order in which a
POM-modifying plugin and `maven-source-plugin` execute differs between
`CI=true` and `CI=false`.

We should almost certainly fix this going forward, for example, by
running the `deploy-release` workflow without the JDK 8 fixups and
reserving those for `build` runs[*].

Piotr

[*] As an aside: the `build` workflow is a misnomer. Its main purpose is
to run unit tests, and building the artifacts is just a side effect.
Conversely, the main purpose of `deploy-release` is to build the
artifacts (without testing) and deploy them to the staging repository.


Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
Hi All,

I tried to adapt the review kit to my setup, running:

sh mvn verify -P docker \
  -Prelease artifact:compare \
  -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325

I get:
...
[INFO] --- artifact:3.6.0:compare (default-cli) @ log4j-bom ---
[INFO] <project.build.outputTimestamp> property (=
2026-05-02T19:54:56Z) is inherited, you can override in pom.xml
Downloading from reference:
https://repository.apache.org/content/repositories/orgapachelogging-1325/org/apache/logging/log4j/log4j-bom/2.26.0/log4j-bom-2.26.0.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-1325/org/apache/logging/log4j/log4j-bom/2.26.0/log4j-bom-2.26.0.pom
Downloaded from reference:
https://repository.apache.org/content/repositories/orgapachelogging-1325/org/apache/logging/log4j/log4j-bom/2.26.0/log4j-bom-2.26.0.pom
(12 kB at 78 kB/s)
Downloading from reference:
https://repository.apache.org/content/repositories/orgapachelogging-1325/org/apache/logging/log4j/log4j-bom/2.26.0/log4j-bom-2.26.0-cyclonedx.xml
Downloaded from reference:
https://repository.apache.org/content/repositories/orgapachelogging-1325/org/apache/logging/log4j/log4j-bom/2.26.0/log4j-bom-2.26.0-cyclonedx.xml
(435 kB at 600 kB/s)
[INFO] Minimal buildinfo generated from downloaded artifacts:
/Users/garygregory/rc/log4j-2.26.0/src/target/reference/log4j-bom-2.26.0.buildinfo
[ERROR] sha512 mismatch log4j-bom-2.26.0-cyclonedx.xml: investigate
with diffoscope
target/reference/org.apache.logging.log4j/log4j-bom-2.26.0-cyclonedx.xml
target/bom.xml
[ERROR] Reproducible Build output summary: 1 files ok, 1 different
[ERROR] see diff target/reference/log4j-bom-2.26.0.buildinfo
target/log4j-bom-2.26.0.buildinfo
[ERROR] see also
https://maven.apache.org/guides/mini/guide-reproducible-builds.html
[INFO] Reproducible Build output comparison saved to
/Users/garygregory/rc/log4j-2.26.0/src/target/log4j-bom-2.26.0.buildcompare
[INFO] Aggregate buildcompare copied to
/Users/garygregory/rc/log4j-2.26.0/src/target/log4j-bom-2.26.0.buildcompare
[INFO] ------------------------------------------------------------------------
...

diff target/reference/log4j-bom-2.26.0.buildinfo
target/log4j-bom-2.26.0.buildinfo
0a1,2
> # https://reproducible-builds.org/docs/jvm/
> buildinfo.version=1.0-SNAPSHOT
1a4,25
> name=Apache Log4j BOM
> group-id=org.apache.logging.log4j
> artifact-id=log4j-bom
> version=2.26.0
>
> # source information
> source.scm.uri=scm:git:https://github.com/apache/logging-log4j2.git
> source.scm.tag=rel/2.25.3
>
> # build instructions
> build-tool=mvn
>
> # effective build environment information
> java.version=17.0.19
> java.vendor=Homebrew
> os.name=Mac OS X
>
> # Maven rebuild instructions and effective environment
> mvn.version=3.9.15
>
> # output
>
10c34
< outputs.1.checksums.sha512=b421514aae72c62eaa47db2d4954b7a3f1d19416bbc8642d6914b5e06ed30f293f5a0557b1d8bc1e4f32578a47c2af38f60fbb5174dfbeb025afb9007cab292b
---
> outputs.1.checksums.sha512=2b2968ac73a5ac4fb38b4dce56ebbb61d044c082beae0053015561d35142b9621799b100efc1a384825fc68f87be1d3ecee675da492a1500fc0adfdf3a39bd48

My set up:

openjdk version "17.0.19" 2026-04-21
OpenJDK Runtime Environment Homebrew (build 17.0.19+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing)

Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349)
Maven home: /opt/homebrew/Cellar/maven/3.9.15/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.4.1", arch: "aarch64", family: "mac"

Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19
19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64

Docker version 29.4.1, build 055a478

Gary

On Mon, May 4, 2026 at 3:47 AM Volkan Yazıcı <vo...@yazi.ci> wrote:
>
> This is a vote to release the Apache Log4j `2.26.0`.
>
> Website: https://logging.staged.apache.org/log4j/2.26.0
> GitHub: https://github.com/apache/logging-log4j2
> Commit: c1ad2a66cc90e643ec319b9e131764c9710bebc5
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.0
> Nexus: https://repository.apache.org:443/content/repositories/orgapachelogging-1325
> 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 minor release delivers all the fixes in the `[2.25.0, 2.25.4]`
> version range, plus some new fixes, and several other
> improvements and features.
>
> === Added
>
> * Add a new `ConfigurationFactory::getConfiguration` method
>   accepting multiple `URI`s (#3775, #3921)
> * Add and export
>   `org.apache.logging.log4j.core.pattern.NamedInstantPattern`
>   enabling users to programmatically access named date
>   & time patterns supported by Pattern Layout (#3789)
> * Add `log4j.plugin.processor.minAllowedMessageKind`
>   annotation processor option to `PluginProcessor` to filter
>   diagnostic messages by severity. This allows builds that
>   treat compiler notes as errors (e.g. Maven with `-Werror`)
>   to suppress informational notes emitted during normal
>   plugin processing. (#3380, #4063)
> * Add missing setters to `Rfc5424LayoutBuilder`
>
> === Changed
>
> * Ensure scripts in the global `Scripts` element have
>   explicit names by throwing a `ConfigurationException`
>   for unnamed ones. (#3176)
> * Simplify file manager registry factory methods (#3968)
>
> === Deprecated
>
> * Deprecated withers in builder classes in favor of setters.
>   This change improves API consistency with Log4j Core
>   3 and helps users adapt to the upcoming changes. (#3750)
>
> === Fixed
>
> * Fix script resolution failure when the `Scripts` element
>   is placed after a `ScriptRef` in the configuration. (#3336)
> * Fix `ArrayIndexOutOfBoundsException` thrown by
>   `ThrowableStackTraceRenderer` when the stack trace
>   is modified concurrently (#3940, #3955)
> * Fix `SLF4JLogger.atFatal()` returning `atLevel(Level.TRACE)`
>   instead of `atLevel(Level.FATAL)`. This was causing
>   `FATAL`-level log events to be silently discarded when using
>   the fluent API through the `log4j-to-slf4j` bridge. (#4068, #4089)
> * Fix Javadoc references across module boundaries
>   (i.e., cross-references) (#4099, #4100)
> * Fix header write in `RollingRandomAccessFileManager` that
>   was being incorrectly skipped if `append=true` and the file
>   didn't exist before
> * Fix a properties file configuration regression caused by not
>   referenced loggers, appenders, and filters (#4036, #4069)
>
> === Removed
>
> * Remove the `jvmrunargs` lookup. (#3874)
>
> === Updated
>
> * Update `org.junit:junit-bom` to version `5.13.4` (#3850)
> * Update `org.mongodb:bson` to version `5.6.1` (#3961)
> * Update `org.xerial.snappy:snappy-java` to version `1.1.10.8` (#3841)

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by Gary Gregory <ga...@gmail.com>.
On Mon, May 4, 2026 at 2:50 PM Piotr P. Karwasz
<pi...@mailing.copernik.eu> wrote:
>
> Hi Volkan,
>
> On 4.05.2026 09:45, Volkan Yazıcı wrote:
> > This is a vote to release the Apache Log4j `2.26.0`.
> >
> > [...]
> >
> > [ ] +1, release the artifacts
> > [ ] -1, don't release, because...
>
>
> +1 (binding), release the artifacts.
>
> I followed the standard verification process:
>
> 1. Verified checksums
> 2. Verified signatures
> 3. Verified the build (unit tests + reproducibility)
>
> For the last step I needed a slightly different invocation:
>
>     chmod a+x mvnw
>     CI=true ./mvnw verify artifact:compare \
>       -Prelease,\!docker \
>
> -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325
>
> I explained the need for `CI=true` in [1]. As for the rest:
>
> - We'll need to either bump `mvnw` to a version that can be invoked
> through `sh`, or replace the custom source archive script with `git
> archive`.

This is what I warned against a while back. We should not stuff a
random old version of Maven on people's machines.

Gary

> - My version of Docker doesn't play well with the `docker-maven-plugin`
> version used in the build, so I had to skip the Docker tests.
>
> Note also that the CI build had one failure in
> `integration-test (2.26.0) / build (windows-latest)`:
>
>   https://github.com/apache/logging-log4j2/actions/runs/25259932526
>
> This failure is unrelated to the released version: it's a bug in an
> integration test that was only exercised on UNIX.
>
> Thank you for seeing this release through, Volkan. This one wasn't easy,
> with the long gap since the last minor release and the various build
> issues along the way, and I really appreciate you carrying it across the
> finish line.
>
> Piotr
>
> [1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj

Re: [VOTE] Release Apache Log4j `2.26.0`

Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Volkan,

On 4.05.2026 09:45, Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j `2.26.0`.
>
> [...]
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...


+1 (binding), release the artifacts.

I followed the standard verification process:

1. Verified checksums
2. Verified signatures
3. Verified the build (unit tests + reproducibility)

For the last step I needed a slightly different invocation:

    chmod a+x mvnw
    CI=true ./mvnw verify artifact:compare \
      -Prelease,\!docker \

-Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325

I explained the need for `CI=true` in [1]. As for the rest:

- We'll need to either bump `mvnw` to a version that can be invoked
through `sh`, or replace the custom source archive script with `git
archive`.
- My version of Docker doesn't play well with the `docker-maven-plugin`
version used in the build, so I had to skip the Docker tests.

Note also that the CI build had one failure in
`integration-test (2.26.0) / build (windows-latest)`:

  https://github.com/apache/logging-log4j2/actions/runs/25259932526

This failure is unrelated to the released version: it's a bug in an
integration test that was only exercised on UNIX.

Thank you for seeing this release through, Volkan. This one wasn't easy,
with the long gap since the last minor release and the various build
issues along the way, and I really appreciate you carrying it across the
finish line.

Piotr

[1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj

[RESULT][VOTE] Release Apache Log4j `2.26.0`

Posted by Volkan Yazıcı <vo...@yazi.ci>.
Adding my +1.

With that, the release passes with 4 binding +1 votes from Jan, Piotr,
Gary, and me. I will continue the release process.

On Mon, May 4, 2026 at 9:45 AM Volkan Yazıcı <vo...@yazi.ci> wrote:
>
> This is a vote to release the Apache Log4j `2.26.0`.
>
> Website: https://logging.staged.apache.org/log4j/2.26.0
> GitHub: https://github.com/apache/logging-log4j2
> Commit: c1ad2a66cc90e643ec319b9e131764c9710bebc5
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.0
> Nexus: https://repository.apache.org:443/content/repositories/orgapachelogging-1325
> 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 minor release delivers all the fixes in the `[2.25.0, 2.25.4]`
> version range, plus some new fixes, and several other
> improvements and features.
>
> === Added
>
> * Add a new `ConfigurationFactory::getConfiguration` method
>   accepting multiple `URI`s (#3775, #3921)
> * Add and export
>   `org.apache.logging.log4j.core.pattern.NamedInstantPattern`
>   enabling users to programmatically access named date
>   & time patterns supported by Pattern Layout (#3789)
> * Add `log4j.plugin.processor.minAllowedMessageKind`
>   annotation processor option to `PluginProcessor` to filter
>   diagnostic messages by severity. This allows builds that
>   treat compiler notes as errors (e.g. Maven with `-Werror`)
>   to suppress informational notes emitted during normal
>   plugin processing. (#3380, #4063)
> * Add missing setters to `Rfc5424LayoutBuilder`
>
> === Changed
>
> * Ensure scripts in the global `Scripts` element have
>   explicit names by throwing a `ConfigurationException`
>   for unnamed ones. (#3176)
> * Simplify file manager registry factory methods (#3968)
>
> === Deprecated
>
> * Deprecated withers in builder classes in favor of setters.
>   This change improves API consistency with Log4j Core
>   3 and helps users adapt to the upcoming changes. (#3750)
>
> === Fixed
>
> * Fix script resolution failure when the `Scripts` element
>   is placed after a `ScriptRef` in the configuration. (#3336)
> * Fix `ArrayIndexOutOfBoundsException` thrown by
>   `ThrowableStackTraceRenderer` when the stack trace
>   is modified concurrently (#3940, #3955)
> * Fix `SLF4JLogger.atFatal()` returning `atLevel(Level.TRACE)`
>   instead of `atLevel(Level.FATAL)`. This was causing
>   `FATAL`-level log events to be silently discarded when using
>   the fluent API through the `log4j-to-slf4j` bridge. (#4068, #4089)
> * Fix Javadoc references across module boundaries
>   (i.e., cross-references) (#4099, #4100)
> * Fix header write in `RollingRandomAccessFileManager` that
>   was being incorrectly skipped if `append=true` and the file
>   didn't exist before
> * Fix a properties file configuration regression caused by not
>   referenced loggers, appenders, and filters (#4036, #4069)
>
> === Removed
>
> * Remove the `jvmrunargs` lookup. (#3874)
>
> === Updated
>
> * Update `org.junit:junit-bom` to version `5.13.4` (#3850)
> * Update `org.mongodb:bson` to version `5.6.1` (#3961)
> * Update `org.xerial.snappy:snappy-java` to version `1.1.10.8` (#3841)