+1

I tested the src zip file distribution:

- GPG ok
- SHA512 OK
- mvn clean verify

But it failed with Docker tests enabled: mvn clean verify -Pdocker
-D'docker.showLogs=true'

[ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after
60764 ms while waiting on tcp port '[/172.19.0.2:9200]'
[ERROR] DOCKER> Error occurred during container startup, shutting down...
<deleted "ES" output>
[INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and
removed container a095e36ff18f after 0 ms
[ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch":
Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9200]']

Using:

openjdk version "17.0.15" 2025-04-15
OpenJDK Runtime Environment Homebrew (build 17.0.15+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.15+0, mixed mode, sharing)

Apache Maven 3.9.10 (5f519b97e944483d878815739f519b2eade0a91d)
Maven home: /opt/homebrew/Cellar/maven/3.9.10/libexec
Java version: 17.0.15, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@17/17.0.15/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac"

Darwin ****.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22
19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64

Docker version 28.3.0, build 38b7060

Gary

On Sat, Jul 5, 2025 at 5:08 PM Piotr P. Karwasz
<pi...@mailing.copernik.eu> wrote:
>
> This is a vote to release the Apache Log4j `2.25.1`.
>
> Website: https://logging.staged.apache.org/log4j/2.25.1/index.html
> GitHub: https://github.com/apache/logging-log4j2
> Commit: bda63362cf405449ff4edc2e4d92353be65c4d4e
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.25.1
> Nexus:
> https://repository.apache.org:443/content/repositories/orgapachelogging-1320
> 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.
> You can optionally also cast your vote in the ATR system[**].
>
> [ ] +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.
>
> [*] As with the 2.25.0 release, the aggregate SBOM for the log4j-bom
> artifact in version 2.25.1 is not fully reproducible. Two variants may
> be generated that differ only in the ordering of the `jspecify` dependency.
>
> This issue is known and tracked under GitHub issue #3804:
>
> https://github.com/apache/logging-log4j2/issues/3804
>
> To avoid false negatives during verification, reviewers are asked to
> ignore this specific difference by appending the following parameter to
> the build command in the release review instructions:
>
> -Dbuildinfo.ignore="*/log4j-bom-2.25.1-cyclonedx.xml"
>
> [**] Please note that the Apache Trusted Release (ATR) tool is currently
> in alpha, and votes cast through ATR are not officially counted in the
> release process. However, Apache committers are encouraged to try it out
> and provide feedback using the following URL:
>
> https://release-test.apache.org/vote/logging-log4j/2.25.1
>
> == Release Notes
>
> 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.
>
> The complete changelog of the `2.25.1` release can be found on the
> staged website at:
>
> https://logging.staged.apache.org/log4j/2.25.1/release-notes.html#release-notes-2-25-1

Reply via email to