[ANNOUNCE] Apache Log4j `2.25.1` released

The Apache Log4j team is pleased to announce the `2.25.1` release. Apache Log4j is a versatile, industrial-strength Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. == Release Notes This patch release addresses a dozen

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

Hi all, On 5.07.2025 23:08, Piotr P. Karwasz wrote: > 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

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

754 Although most of these annotations are in `log4j-core`—which shouldn't typically be on users' compile classpaths—many projects still include it during compilation, intentionally or not. ## Episode 4: Enter GMM Adding runtime dependencies just to silence compile-time linter warn

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

to appear in the -sources.jar. > > By the way: since XML comments can be ignored by parsers, they’re stripped > out by the Flatten Plugin before the final pom.xml is written. Kudos to > whoever chose to use a comment rather than something like a > published-with-gradle-metadata propert

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

something like a |published-with-gradle-metadata| property. Best, Piotr PS: I attach my result of running `diffoscope` below: --- log4j-api/target/reference/org.apache.logging.log4j/log4j-api-2.25.1-sources.jar +++ log4j-api/target/log4j-api-2.25.1-sources.jar ├── zipinfo {} │ @@ -1,8 +1,8 @@ │ -Zip

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

top generating the optional `createdBy` field altogether: > > https://github.com/gradlex-org/gradle-module-metadata-maven-plugin/issues/43 > > This should improve reproducibility and make it easier to verify future > Log4j releases. > >> The diffoscope output for the

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

the optional `createdBy` field altogether: https://github.com/gradlex-org/gradle-module-metadata-maven-plugin/issues/43 This should improve reproducibility and make it easier to verify future Log4j releases. > The diffoscope output for the other file has substantial changes > (probably related t

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

The diffoscope output for the module file is simple: diffoscope log4j-api/target/reference/org.apache.logging.log4j/log4j-api-2.25.1.module log4j-api/target/publications/maven/module.json --- log4j-api/target/reference/org.apache.logging.log4j/log4j-api-2.25.1.module +++ log4j-api/target

[DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

Hi Volkan, On 8.07.2025 09:29, Volkan Yazıcı wrote: > I could not resolve the `artifact:compare` failure on > `log4j-parent`. This is an important problem, but not > a release blocker, AFAICT. Just to clarify—are you referring to the reproducibility issue in `log4j-bom`, or is this a

[log4j] Links to issues in VOTE emails and release notes (Was: [VOTE] Release Apache Log4j `2.25.1` (RC1))

: > 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/lo

[DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

.mvn/wrapper/maven-wrapper.properties This is a known bug in Maven Wrapper—see Volkan's e-mail. > When I tried running the build with a local copy of Maven, I get a different > error: > > [ERROR] size mismatch log4j-api-2.25.1-sources.jar: investigate with > di

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

a PR[3], yet... I could not resolve the `artifact:compare` failure on `log4j-parent`. This is an important problem, but not a release blocker, AFAICT. [1] https://issues.apache.org/jira/browse/MWRAPPER-161 [2] https://github.com/apache/maven-wrapper/issues/305 [3] https://github.com/apache/maven

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

copy of Maven, I get a different error: [ERROR] size mismatch log4j-api-2.25.1-sources.jar: investigate with diffoscope log4j-api/target/reference/org.apache.logging.log4j/log4j-api-2.25.1-sources.jar log4j-api/target/log4j-api-2.25.1-sources.jar [ERROR] size mismatch log4j-api-2.25.1.module

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

On Sat, Jul 5, 2025 at 5:54 PM Piotr P. Karwasz wrote: > > Hi Gary, > > On 5.07.2025 23:41, Gary Gregory wrote: > > But it failed with Docker tests enabled: mvn clean verify -Pdocker > > -D'docker.showLogs=true' > > > > [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after > > 6076

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

Hi Gary, On 5.07.2025 23:41, Gary Gregory wrote: > 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> Er

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

ot;, 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

[VOTE] Release Apache Log4j `2.25.1` (RC1)

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

Re: [D] Log4j creates an empty log file and refuses to fill it? [logging-log4j2]

GitHub user i-make-robots edited a comment on the discussion: Log4j creates an empty log file and refuses to fill it? Whoops. GitHub link: https://github.com/apache/logging-log4j2/discussions/3793#discussioncomment-13636074 This is an automatically sent email for dev@logging.apache.org

Re: [D] Log4j creates an empty log file and refuses to fill it? [logging-log4j2]

GitHub user i-make-robots added a comment to the discussion: Log4j creates an empty log file and refuses to fill it? Whoops.Sent from my iPhoneOn Jul 1, 2025, at 11:54 AM, Piotr P. Karwasz ***@***.***> wrote: Hi @i-make-robots, My Java 22 open source project is https://github.

Re: [D] Log4j creates an empty log file and refuses to fill it? [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: Log4j creates an empty log file and refuses to fill it? Hi @i-make-robots, > My Java 22 open source project is > [https://github.com/MarginallyClever/Makelangelo-software/](https://github.com/MarginallyClever/Makelangelo-so

Re: [D] Log4j creates an empty log file and refuses to fill it? [logging-log4j2]

GitHub user i-make-robots edited a discussion: Log4j creates an empty log file and refuses to fill it? Hello, everyone. I hope you're doing well. My Java 22 open source project is https://github.com/MarginallyClever/Makelangelo-software/. I'm using logback and log4j with a ro

[ANNOUNCE] Apache Log4j `2.25.0` released

The Apache Log4j team is pleased to announce the `2.25.0` release. Apache Log4j is a versatile, industrial-strength Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. For further information (support, download, etc.) see

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

Hi all, On 13.06.2025 20:59, Piotr P. Karwasz wrote: > This is a vote to release the Apache Log4j `2.25.0`. > > Website: https://logging.staged.apache.org/log4j/2.25.0/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: ea10ad3e78469e43f138853b8c9892bc51bc87ec

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

+1 ✅ Signatures ✅ Checksums ✅ Build *Build command:* ./mvnw verify \ -Prelease \ -Dbuildinfo.ignore="*/log4j-bom-2.25.0-cyclonedx.xml" \ artifact:compare \ -Dreference.repo= https://repository.apache.org:443/content/repositories/orgapachelogging-13

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

:59, Piotr P. Karwasz wrote: This is a vote to release the Apache Log4j `2.25.0`. Website: https://logging.staged.apache.org/log4j/2.25.0/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: ea10ad3e78469e43f138853b8c9892bc51bc87ec Distribution: https://dist.apache.org/repos/dist/dev

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

+1 If I don't enable Docker, then the whole build passes, I can validate the src zip file with: mvn clean verify FWIW, you can't just exclude "log4j-layout-template-json-test" with: mvn clean verify -Pdocker -D'docker.showLogs=true' -pl '!log4j-layout-t

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

7.512Z", "log.level": "INFO", "message":"closed", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutd

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

s valid on Linux, but may not hold on macOS. You might want to try omitting the host name altogether: elasticsearch.port:9200 If that works, please submit a PR to fix the issue in `log4j-layout-template-json` and `log4j-mongodb`. Piotr

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

> > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Start container > > e514938157d8 > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Network mode: > > log4j-layout-template-json-network > > [INFO] DOCKER> [elasticsearch:8.17.3] "

[DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

> [INFO] DOCKER> Status: Downloaded newer image for logstash:8.17.3 > [INFO] DOCKER> Pulled logstash:8.17.3 in 27 seconds > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Start container > e514938157d8 > [INFO] DOCKER> [elasticsearch:8.17.3] "ela

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

in 27 seconds > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Start container > e514938157d8 > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Network mode: > log4j-layout-template-json-network > [INFO] DOCKER> [elasticsearch:8.17.3] "

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

R> [elasticsearch:8.17.3] "elasticsearch": Start container e514938157d8 [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Network mode: log4j-layout-template-json-network [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Waiting for ports [9200] directly on contai

[VOTE] Release Apache Log4j `2.25.0` (RC1)

This is a vote to release the Apache Log4j `2.25.0`. Website: https://logging.staged.apache.org/log4j/2.25.0/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: ea10ad3e78469e43f138853b8c9892bc51bc87ec Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.25.0 Nexus

Re: [D] log4j version 2.17.1 [logging-log4j2]

GitHub user ppkarwasz edited a comment on the discussion: log4j version 2.17.1 > Could you please confirm if Log4j version 2.17.1 is supported? Whether we "support" Log4j version `2.17.0` depends on how you define "support," so let’s break it down: - We **no longer

Re: [D] log4j version 2.17.1 [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: log4j version 2.17.1 > Could you please confirm if Log4j version 2.17.1 is supported? Whether we "support" Log4j version `2.17.0` depends on how you define "support," so let’s break it down: - We **no longer

Re: [D] log4j version 2.17.1 [logging-log4j2]

GitHub user mmahant17 added a comment to the discussion: log4j version 2.17.1 Thank you for your prompt response. GitHub link: https://github.com/apache/logging-log4j2/discussions/3679#discussioncomment-13212196 This is an automatically sent email for dev@logging.apache.org. To

Re: [D] log4j version 2.17.1 [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: log4j version 2.17.1 That’s an excellent answer — thank you! Just to add for completeness: version 2.17.0 was never affected by CVE-2021-44832. This was confirmed in a later review (see apache/logging-site#6). GitHub link: https

Re: [D] log4j version 2.17.1 [logging-log4j2]

GitHub user perry2of5 added a comment to the discussion: log4j version 2.17.1 Please refer to the security page: https://logging.apache.org/security.html Also, mvnrepository.com provides links to most security vulnerabilities from affected artifacts. For example, on log4j-core, it doesn&#

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 Reload4j is a **valid temporary** replacement for Log4j 1, and I can certainly recommend it for that purpose. While it introduces some breaking changes compared to Log4j `1.2.17`, it is **99

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 @ElaHuskovic68, > This is third party application, I dont have source code, only war file which > contains 1.x version of log4j jar file. Thanks for clarifying your situation — dealin

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ppkarwasz edited a comment on the discussion: log4j-1.2.13.jar substitution in v.2.17.1 @ElaHuskovic68, > This is third party application, I dont have source code, only war file which > contains 1.x version of log4j jar file. Thanks for clarifying your situation — dealin

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user lalo-mx added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 > Some people have been known to recommend Reload4j 1.2.18 as a replacement for > log4j 1.2.17 https://reload4j.qos.ch/ > Initiated by Ceki Gülcü, the original author of Apache log4j

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user perry2of5 added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 Some people have been known to recommend Reload4j 1.2.18 as a replacement for log4j 1.2.17 GitHub link: https://github.com/apache/logging-log4j2/discussions/3656#discussioncomment-13135934

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ElaHuskovic68 added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 hi @ppkarwasz - thank you for your answer. This is third party application, I dont have source code, only war file which contains 1.x version of log4j jar file. I checked with Owner and it

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 Can you provide us with some feedback on the migration page? Where does it come short of your expectations? To better understand, how we can help, can you tell us: - Do you have access to the

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ElaHuskovic68 edited a discussion: log4j-1.2.13.jar substitution in v.2.17.1 Inside war file at path /WEB-INF/lib we found log4j-1.2.13 which needs to be replaced with log4j-2.17.1.jar. In apache-log4j-2.17.1-bin there is no that file. What jar file replaces old one? Thanks

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user ElaHuskovic68 added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 Not in our case. We though just to replace .jar file but no proper match in higher version. GitHub link: https://github.com/apache/logging-log4j2/discussions/3656#discussioncomment

Re: [D] log4j-1.2.13.jar substitution in v.2.17.1 [logging-log4j2]

GitHub user vy added a comment to the discussion: log4j-1.2.13.jar substitution in v.2.17.1 @ElaHuskovic68, does the [Migrating from Log4j 1](https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html) page help? GitHub link: https://github.com/apache/logging-log4j2/discussions/3656

Re: log4j 3.0 feature request: Jackson 3.0

Hi Clayton, On 5.05.2025 23:00, Clayton Wohl wrote: The current log4j 3.0 beta builds use Jackson 2.x. My request is that log4j 3.0 development switch to Jackson 3.0 RC builds. This would mean that a final log4j 3.0 would be dependent on a final Jackson 3.0, but it looks like Jackson 3.0 will

log4j 3.0 feature request: Jackson 3.0

The current log4j 3.0 beta builds use Jackson 2.x. My request is that log4j 3.0 development switch to Jackson 3.0 RC builds. This would mean that a final log4j 3.0 would be dependent on a final Jackson 3.0, but it looks like Jackson 3.0 will release first anway. Jackson 3.0 is a large upgrade

[RESULT] [VOTE] Add branch protection rules to Log4j

Hi, These are my votes: On 2.04.2025 19:12, Piotr P. Karwasz wrote: Vote 1. Require a pull request before merging: [ ] +1, enable this feature [ ] -1, do not enable this feature +1 Vote 2. Require conversation resolution before merging: [ ] +1, enable this feature [ ] -1, do not enable this

Re: [VOTE] Add branch protection rules to Log4j

Hi all, Sorry, my e-mail client reformatted some lines. So, the concerned repos are all non-dormant Java repos: l-admin, l-jdk, l-jmx-gui, l-log4j2, l-log4j-jakarta, l-log4j-kotlin, l-log4j-samples, l-log4j-scala, l-log4j-transform, l-log4j-tools, l-parent. Vote 1. Require a pull request

Re: [VOTE] Add branch protection rules to Log4j

e GitHub > Settings. This is a vote to decide whether or not enable certain branch > protection features on the code branches (`2.x` and `main`) of these repos: > > * l-admin * l-jdk * l-jmx-gui > * l-log4j2 * l-log4j-jakarta * l-log4j-kotlin * l-log4j-samples* > l-log4j-sca

Re: [VOTE] Add branch protection rules to Log4j

Hi, Vote 1. Require a pull request before merging: +1 Vote 2. Require conversation resolution before merging: +1 Vote 3. Require linear history (Prevent merge commits from being pushed to code branches. Only "Squash" and similar allowed): -0.9 I really like a linear history, but I see some prob

Re: [VOTE] Add branch protection rules to Log4j

On Wed, Apr 2, 2025 at 7:12 PM Piotr P. Karwasz wrote: > Hi all, > Sorry, my e-mail client reformatted some lines. > So, the concerned repos are all non-dormant Java repos: l-admin, l-jdk, > l-jmx-gui, l-log4j2, l-log4j-jakarta, l-log4j-kotlin, l-log4j-samples, > l-log4j-scala, l-

Re: [VOTE] Add branch protection rules to Log4j

On Fri, Apr 4, 2025 at 4:07 AM Volkan Yazıcı wrote: > > On Wed, Apr 2, 2025 at 7:12 PM Piotr P. Karwasz > wrote: > > > Hi all, > > Sorry, my e-mail client reformatted some lines. > > So, the concerned repos are all non-dormant Java repos: l-admin, l-jdk, > >

Re: [VOTE] Add branch protection rules to Log4j

OK. With the new descriptions I can vote on this. > On Apr 2, 2025, at 10:12 AM, Piotr P. Karwasz > wrote: > > Hi all, > Sorry, my e-mail client reformatted some lines. > So, the concerned repos are all non-dormant Java repos: l-admin, l-jdk, > l-jmx-gui, l-log4j2, l-l

[VOTE] Add branch protection rules to Log4j

these repos: * l-admin * l-jdk * l-jmx-gui * l-log4j2 * l-log4j-jakarta * l-log4j-kotlin * l-log4j-samples* l-log4j-scala * l-log4j-transform * l-log4j-tools * l-parent * l-slf4j (i.e. all the Java repos except Chainsaw, Flume and Log4j Audit). The vote will be open for 176 hours (1 week

Re: [VOTE] Add branch protection rules to Log4j

Hi Ralph, On 2.04.2025 17:40, Ralph Goers wrote: I am finding this email confusing. I think it is due to the > formatting but I am not sure. I am making my best guess. Sorry, the e-mail client ate some new line characters. Vote 1: Enable certain branch protection features on the code > branc

Re: Any updates on log4j 3.0.0 becoming GA?

cut this 3.0.0 release? I believe a vote has > > to be called? > > Since January no maintainer can contribute to Log4j as part of their > dayjob, so the development of Log4j has been processing at an extremely > slow pace. Optimistically we can dedicate maybe 8 hours a week to the &

Re: Any updates on log4j 3.0.0 becoming GA?

Hi Daniel, On 17.03.2025 15:19, Daniel Burrell wrote: Is a maintainer available to cut this 3.0.0 release? I believe a vote has to be called? Since January no maintainer can contribute to Log4j as part of their dayjob, so the development of Log4j has been processing at an extremely slow

Re: Any updates on log4j 3.0.0 becoming GA?

, Feb 25, 2025 at 4:37 PM Daniel Burrell wrote: > Hi logging team, > > Perhaps if there are no further concerns, would it be possible for one of > the maintainers to please cut a release of log4j 3.0? > > Kind regards > > Daniel Burrell > > > On Wed, 29 Jan 2025

Re: Any updates on log4j 3.0.0 becoming GA?

isabled on github repo for some reason. > > > > Kind regards, > > > > Daniel Burrell > > > > > > On Tue, Feb 25, 2025 at 4:37 PM Daniel Burrell > > wrote: > > > > > Hi logging team, > > > > > > Perhaps if there are n

Re: Any updates on log4j 3.0.0 becoming GA?

aniel Burrell > wrote: > > > Hi logging team, > > > > Perhaps if there are no further concerns, would it be possible for one of > > the maintainers to please cut a release of log4j 3.0? > > > > Kind regards > > > > Daniel Burrell >

Re: [log4j] Help with updating projects to `logging-parent` version `12.0.0`

me > with updating these 9 projects, please?* (I can explain what needs to be > done for this `logging-parent` update.) > > P.S. This new `logging-parent` update is crucial for the upcoming Log4j > `2.25.0` release, since it fixes the BOM bug reported by Spring > <https://github.com/apache/logging-log4j2/issues/3066>. >

Re: Log4j-spring-boot is still required in Spring Boot 3

application will fail to start. This behavior is different then >> what log4j-spring-boot does. It seems that if you include the >> log4j-spring-boot jar then the error is avoided. > > IMHO the `Log4j2LoggingSystem` (both ours and the one in Spring Boot 3) has a >

Re: Any updates on log4j 3.0.0 becoming GA?

Hi logging team, Perhaps if there are no further concerns, would it be possible for one of the maintainers to please cut a release of log4j 3.0? Kind regards Daniel Burrell On Wed, 29 Jan 2025 at 23:35, Daniel Burrell wrote: > Dear Apache Logging team, > > > We've been te

Re: Log4j-spring-boot is still required in Spring Boot 3

Hi Ralph, On 25.02.2025 14:36, Ralph Goers wrote: Just an FYI - in Spring Boot 3 if you specify an override file that is not present the application will fail to start. This behavior is different then what log4j-spring-boot does. It seems that if you include the log4j-spring-boot jar then

Log4j-spring-boot is still required in Spring Boot 3

Just an FYI - in Spring Boot 3 if you specify an override file that is not present the application will fail to start. This behavior is different then what log4j-spring-boot does. It seems that if you include the log4j-spring-boot jar then the error is avoided. See https://github.com/spring

[log4j] Help with updating projects to `logging-parent` version `12.0.0`

. I am swamped with PR reviews and other maintenance tasks – AFAIK, Piotr too. *Could anybody help me with updating these 9 projects, please?* (I can explain what needs to be done for this `logging-parent` update.) P.S. This new `logging-parent` update is crucial for the upcoming Log4j `2.25.0` r

Any updates on log4j 3.0.0 becoming GA?

Dear Apache Logging team, We've been testing log4j beta3 with much success and appreciate the clear migration documentation, as well as support from ppkarwasz (thank you!). Could you provide any information about the expected timeline for the release of log4j 3.0.0 GA? Is this somethi

[log4j] JEP 502: Stable Values

#TIL JEP 502 <https://openjdk.org/jeps/502> contains several examples employing logger initialization and other things (e.g., holder idiom for lazy initialization) that we use in Log4j.

[ANNOUNCE] Apache Log4j `2.24.3` released

The Apache Log4j team is pleased to announce the `2.24.3` release. Apache Log4j is a versatile, industrial-strength Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. For further information (support, download, etc.) see

[RESULT][VOTE] Release Apache Log4j 2.24.3 (RC1)

Hi all, On 10.12.2024 14:56, Gary Gregory wrote: Running 'mvn clean verify' succeeds, so +1. Gary And here is my +1. With it the vote passes with 3 binding +1 from Gary Gregory, Jan Friedrich and myself. I will continue the release process. Piotr

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

, December 10, 2024, 12:29:48 PM, you wrote: > This is a vote to release the Apache Log4j `2.24.3`. > Website: https://logging.staged.apache.org/log4j/2.24.3/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: 4aa5efec7f2ee2d4623381cd66c3df3a16a6b9a9 > Dist

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

get/bom.xml > > target/reference/org.apache.logging.log4j/log4j-bom-2.24.3-cyclonedx.xml > > 2445,2452c2445,2452 > > < 85497a1ab65d101400ba4073c7d0c839 > > < alg="SHA-1">f384ad3659c6f2529dc5f3516d24e26092c74eca > > < > > alg="S

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

Hi Gary, On 10.12.2024 17:18, Gary Gregory wrote: Here you go: diff target/bom.xml target/reference/org.apache.logging.log4j/log4j-bom-2.24.3-cyclonedx.xml 2445,2452c2445,2452 < 85497a1ab65d101400ba4073c7d0c839 < f384ad3659c6f2529dc5f3516d24e26092

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

achelogging-1309 > > > > diff target/reference/log4j-bom-2.24.3.buildinfo > > target/log4j-bom-2.24.3.buildinfo > > The `*.buildinfo` files are pretty much useless, they only give you some > information on the system the performed the build. It doesn't even > contain al

[DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

Hi Gary, On 10.12.2024 14:58, Gary Gregory wrote: Here you go: mvn verify -Prelease artifact:compare -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 diff target/reference/log4j-bom-2.24.3.buildinfo target/log4j-bom-2.24.3.buildinfo The `*.buildinfo

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

Piotr, Here you go: mvn verify -Prelease artifact:compare -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 diff target/reference/log4j-bom-2.24.3.buildinfo target/log4j-bom-2.24.3.buildinfo 0a1,2 > # https://reproducible-builds.org/docs/

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

chelogging-1309 > > Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper > > might be compromised. > > Investigate or delete > > /Users/garydgregory/rc/log4j-2.24.3/src/.mvn/wrapper/maven-wrapper.jar > > to attempt a clean download. > > If you updated y

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

fy artifact:compare` twice and there are no differences in the generated artifacts. [ERROR] sha512 mismatch log4j-bom-2.24.3-cyclonedx.xml: investigate with diffoscope target/reference/org.apache.logging.log4j/log4j-bom-2.24.3-cyclonedx.xml target/bom.xml Any ideas? Can you compare the two files above? Piotr

[DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

or delete /Users/garydgregory/rc/log4j-2.24.3/src/.mvn/wrapper/maven-wrapper.jar to attempt a clean download. If you updated your Maven version, you need to update the specified wrapperSha256Sum property. Could you investigate what is going on, e.g. with: MVNW_VERBOSE=true sh mvnw validate -N

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

Using: mvn verify -Prelease artifact:compare -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 (Should' we also say "clean"?) I get: [INFO] --- artifact:3.5.1:compare (default-cli) @ log4j-bom --- [WARNING] property is inherited, it shoul

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

elete /Users/garydgregory/rc/log4j-2.24.3/src/.mvn/wrapper/maven-wrapper.jar to attempt a clean download. If you updated your Maven version, you need to update the specified wrapperSha256Sum property. zsh: no such file or directory: -Dreference.repo=https://repository.apache.org/content/reposit

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

I'm following the review kit and I get: On Tue, Dec 10, 2024 at 6:31 AM Piotr P. Karwasz wrote: > > This is a vote to release the Apache Log4j `2.24.3`. > > Website: https://logging.staged.apache.org/log4j/2.24.3/index.html > GitHub: https://github.com/apache/log

[VOTE] Release Apache Log4j 2.24.3 (RC1)

This is a vote to release the Apache Log4j `2.24.3`. Website: https://logging.staged.apache.org/log4j/2.24.3/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: 4aa5efec7f2ee2d4623381cd66c3df3a16a6b9a9 Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.24.3

Re: [log4j] CL leak in `ThrowableProxy` (#3282)

Hi Volkan, Yes. It's working now. Thanks! Volkan Yazıcı 於 2024年12月10日 週二 上午4:03寫道： > Alan, I am told by INFRA that your Slack account is reactivated – see > INFRA-26355 . Could > you verify and let me know, please? > > On Fri, Dec 6, 2024 at 2:

Re: [log4j] CL leak in `ThrowableProxy` (#3282)

Alan, I am told by INFRA that your Slack account is reactivated – see INFRA-26355 . Could you verify and let me know, please? On Fri, Dec 6, 2024 at 2:29 PM Volkan Yazıcı wrote: > Alan, do you have time to investigate #3282 >

Re: [log4j] CL leak in `ThrowableProxy` (#3282)

Hi Volkan, Sure. I will follow it on Github issue. Volkan Yazıcı 於 2024年12月6日 週五 下午10:29寫道： > Alan, do you have time to investigate #3282 > , please? 😇 > > I see that your Slack guest account has been deactivated, I guess due to > expiration.

[log4j] CL leak in `ThrowableProxy` (#3282)

Alan, do you have time to investigate #3282 , please? 😇 I see that your Slack guest account has been deactivated, I guess due to expiration. 🤦 I will try to reactivate it.

Re: Compatibility between Log4j API and implementation

Hi Gary, On 28.11.2024 23:06, Piotr P. Karwasz wrote: On 28.11.2024 16:00, Gary Gregory wrote: This is beyond confusing and a new kind of "soft" jar hell IMO. I read this twice and I have no idea how a user would make sense of this. Log4j 2.x should be all in sync, all jars

Re: Compatibility between Log4j API and implementation

This is beyond confusing and a new kind of "soft" jar hell IMO. I read this twice and I have no idea how a user would make sense of this. Log4j 2.x should be all in sync, all jars should be released with each version and match. Period. IMO. Gary On Thu, Nov 28, 2024, 9:52 AM Piotr

Re: Compatibility between Log4j API and implementation

Hi Ralph, On 14.11.2024 19:46, Ralph Goers wrote: Log4j core has a version compatibility comparison just for this reason. If core is updated to require some new feature in the API then the version it checks for needs to be updated and Log4j-API needs to update its version when it adds new

RE: [RESULT][VOTE] Release Apache Log4j `2.24.2` (RC1)

arwasz Sent: Thursday, November 21, 2024 4:22 PM To: dev@logging.apache.org Subject: [RESULT][VOTE] Release Apache Log4j `2.24.2` (RC1) [EXTERNAL EMAIL] + [WEB LINK DETECTED] On 18.11.2024 22:32, Piotr P. Karwasz wrote: > This is a vote to release the Apache Log4j `2.24.2`. > &

[ANNOUNCE] Apache Log4j `2.24.2` released

The Apache Log4j team is pleased to announce the `2.24.2` release. Apache Log4j is a versatile, industrial-strength Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. For further information (support, download, etc.) see

[RESULT][VOTE] Release Apache Log4j `2.24.2` (RC1)

On 18.11.2024 22:32, Piotr P. Karwasz wrote: This is a vote to release the Apache Log4j `2.24.2`. Website: https://logging.staged.apache.org/log4j/2.24.2/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: e65538dc75b52fd2f3e49d4ab5d7b40b376abb89 Distribution: https

[DISCUSS][VOTE] Release Apache Log4j `2.24.2` (RC1)

Hi Gary, On 19.11.2024 00:12, Gary D. Gregory wrote: Sadly, I can never seem to get a Windows build (I'll switch to my macOS box in few mins): Most flaky tests are due to some race condition in the test. These race conditions appear more often on slow OSes and Windows is the slowest one. Ac

Re: [VOTE] Release Apache Log4j `2.24.2` (RC1)

pache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: C:\java\apache-maven-3.9.9 > Java version: 17.0.13, vendor: Eclipse Adoptium, runtime: C:\Program > Files\Eclipse Adoptium\jdk-17.0.13.11-hotspot > Default locale: en_US, platform encoding: UTF-8 > OS name: &qu

Re: [VOTE] Release Apache Log4j `2.24.2` (RC1)

lipse Adoptium, runtime: C:\Program Files\Eclipse Adoptium\jdk-17.0.13.11-hotspot Default locale: en_US, platform encoding: UTF-8 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" ~ Docker version 27.3.1, build ce12230 Gary On 2024/11/

  1   2   3   4   5   6   7   8   9   10   >