[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 b

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 vot

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

Hi Gary, On 9.07.2025 14:35, Gary Gregory wrote: > Dare I ask my our build has Gradle horror in it? It’s not a horror—it’s a tragedy. A well-intentioned series of events that slowly spiraled into pain: ## Episode 1: Runtime-Invisible Annotations Over the past two years, we began using several

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

Hi Matt, On 8.07.2025 22:14, Matt Sicker wrote: > gist-og-image-54fd7dc0713e.png > gist:54c8222bd8ef3dabd690994ab35d85d2 > > gist.github.com > > >

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

Hi Matt, On 8.07.2025 18:34, Matt Sicker wrote: > The diffoscope output for the module file is simple: > > [...] > │ "createdBy": { > │ "maven": { > │ -"version": "3.9.8" > │ +"version": "3.9.10" > │ } I didn't know about this aspect of the Gradle Mo

[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 separate pro

Release notes, changelog and commits

Hi Volkan, On 8.07.2025 10:44, Volkan Yazıcı wrote: > I see that the most recent VOTE email misses ticket IDs, making it > cumbersome to access associated PRs. I can see the Discussion linked, but > that is not what I am asking for. > > Can we share the Issue/PR IDs in the VOTE emails, please? I

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

Hi Matt, On 7.07.2025 22:34, Matt Sicker wrote: > Something is buggy for me in the Maven wrapper script which causes this error > to print out: > > mvnw: line 114: mvnw/.mvn/wrapper/maven-wrapper.properties: Not a directory > cannot read distributionUrl property in > mvnw/.mvn/wrapper/maven-wra

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

[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:

[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 the

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: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

Hi Gary, On 14.06.2025 13:00, Gary Gregory wrote: > On Sat, Jun 14, 2025 at 3:09 AM Piotr P. Karwasz > wrote: >> I hope this helps you debug what is going on during the ElasticSearch >> startup. > > It appears that port 9200 is published in Docker, but it doesn't se

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

Hi Gary, On 14.06.2025 03:22, Gary Gregory wrote: > Running: > > mvn clean verify -Pdocker > > I.get: > > [INFO] DOCKER> Pulling from library/elasticsearch > [INFO] DOCKER> Digest: > sha256:2cc40b15dff85281ac804e7ff27cbc07b31fdd542e94ea7a2bdb6470e3b6bb68 > [INFO] DOCKER> Status: Downloaded newe

[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:

[ANNOUNCE] Apache Logging Parent `12.1.1` released

Apache Logging Parent team is pleased to announce the `12.1.1` release. This project contains the parent POM for other Maven-based Apache Logging Services projects. For further information (support, download, etc.) see the project website[1]. [1] https://logging.apache.org/logging-parent == Relea

Re: [VOTE][LAZY] Release Apache Logging Parent `12.1.1`

On 10.06.2025 14:17, Piotr P. Karwasz wrote: > This is a lazy-vote to release the Apache Logging Parent `12.1.1`. > > Website: https://logging.staged.apache.org/logging-parent-12.1.1 > GitHub: https://github.com/apache/logging-parent > Commit: 9c01c1092a2c07d779d848232

[VOTE][LAZY] Release Apache Logging Parent `12.1.1`

This is a lazy-vote to release the Apache Logging Parent `12.1.1`. Website: https://logging.staged.apache.org/logging-parent-12.1.1 GitHub: https://github.com/apache/logging-parent Commit: 9c01c1092a2c07d779d848232762e86e174eb70e Distribution: https://dist.apache.org/repos/dist/dev/logging/logging

Re: Release 2.25.0

Hi Volkan, On 27.05.2025 11:57, Volkan Yazıcı wrote: > I haven't been feeling well for a while. Could I have one more week to work > on the remaining work assigned to me, please? I'm really sorry to hear you haven't been feeling well—please take all the time you need to rest and recover. Your hea

Re: Release 2.25.0

Hi all, On 16.05.2025 17:37, Piotr P. Karwasz wrote: > I'm aiming to release Log4j 2.25.0 before the end of the month, with > a release candidate planned for next weekend (May 24th). Just a quick update on the 2.25.0 release timeline: - I’ve merged all the pull requests that were r

Release 2.25.0

Hi all, I'm aiming to release Log4j 2.25.0 before the end of the month, with a release candidate planned for next weekend (May 24th). All PRs currently targeted for this version have been reviewed, and some are ready to be merged: https://github.com/apache/logging-log4j2/milestone/16 If you hav

Re: Improving Dependabot Automation Under New Workflow Requirements

Hi Volkan, On 13.05.2025 11:06, Volkan Yazıcı wrote: > Thanks for chasing this Piotr. Given the recently stagnating Log4j > maintainer time, the workflow of verifying dependabot PRs, adding > associated changelog entries, and automatically merging upon success was a > big time saver for us. I'd re

Improving Dependabot Automation Under New Workflow Requirements

Hi all, As expected, the introduction of required reviews and required checks has made our "automatically merge Dependabot PRs" workflow less automatic. Currently, for each Dependabot PR:   * The commit that adds a changelog entry does not trigger the build workflow and therefore fails the r

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 re

[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

Re: [VOTE] Apache Logging Parent `12.1.0` (RC1)

Hi, On 1.04.2025 18:14, Piotr P. Karwasz wrote: This is a lazy-vote to release the Apache Logging Parent `12.1.0`. Website: https://logging.staged.apache.org/logging-parent-12.1.0 GitHub: https://github.com/apache/logging-parent Commit: c470a36f072ecb716e8aef7c5719d50ff9d1a9dc Distribution

[VOTE] Apache Logging Parent `12.1.0` (RC1)

This is a lazy-vote to release the Apache Logging Parent `12.1.0`. Website: https://logging.staged.apache.org/logging-parent-12.1.0 GitHub: https://github.com/apache/logging-parent Commit: c470a36f072ecb716e8aef7c5719d50ff9d1a9dc Distribution: https://dist.apache.org/repos/dist/dev/logging/loggi

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 befor

[VOTE] Add branch protection rules to Log4j

Hi all, Trying to implement the RTC rules we discussed in September[1] I encountered some problems due to the limitations of the currently available 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 th

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

Maven POM "Developers" section

Hi all, A user report regarding a broken link on `projects.apache.org`[1] brought my attention to the amount of out-of-date metadata we publish: * Our DOAP file has not been updated in ages. It contained out of date links. We should probably regenerate it at each release. On `projects.apache

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 pace

Signaling configuration errors

Hi all, Configuration problems in our builders are handled in multiple ways: 1. Sometimes we call `LOGGER.error` and return `null`. 2. Sometimes we throw an explicit exception. The types of exceptions vary: NPE, IllegalArgumentException, IllegalStateException, etc. There is a `o.a.l.l.core.co

Re: Question: "Garbage-Free" AbstractFilter#filter(...) methods.

Hi Remko, On 2.03.2025 04:27, Remko Popma wrote: In my work we create trading applications that send orders to the stock exchange when market conditions change. If the JVM would decide to stop the world to collect garbage, we might not get the orders sent out in time. Our whole stack (messagi

How to unsubscribe (was: New committer: Jeff Thomas)

Hi Carol, On 1.03.2025 10:56, Carol Brickley wrote: Pleas unsubscribe me To unsubscribe, you need to follow a similar process as the one you used to subscribe: send an e-mail to dev-unsubscr...@logging.apache.org and follow the instruction the bot will send you. For more information see: h

New committer: Jeff Thomas

The Project Management Committee (PMC) for Apache Logging has invited Jeff Thomas to become a committer and we are pleased to announce that he has accepted. Please join us in welcoming Jeff to their new role and responsibility in our project community. Welcome to Apache Logging, Jeff! Piotr On

Re: [log4cxx] bugfix release?

Hi Tobias, On 23.02.2025 13:16, Tobias Frost wrote: (Just an follow up, not sure if the previous mail went through anyways; to make sure I'll CC Robert and Piotr, please feel free to forward the mail if it didn't make it to the list) If you are not subscribed to the mailing list, your mails ar

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 the

Re: [log4cxx] bugfix release?

Hi Robert, On 23.02.2025 04:32, Robert Middleton wrote: Should we do a bugfix release of log4cxx soon? We've just had a release recently, but we have fixed a few bugs with the fuzzing that was just added. Sounds good to me. BTW: Remember to add a tag to: https://reporter.apache.org/addrelea

Re: Anything left for 2.25.0?

Hi Gary, On 3.02.2025 19:51, Gary Gregory wrote: Do you think it's possible to add a test to avoid regressions? It is hard to reproduce the problem in a test. There are actually two problems: 1. Something happens during the creation of a new logger that stops the process in some environmen

Re: Issue 3207 - Add support to Compact Log Event Format

Hi Jay, On 23.01.2025 06:15, Jay Katariya wrote: Before I start the discussion here, I want to mention I am a Log4j newbie contributor, and don't know feature requests etc work, and what is a good feature vs what is not a good feature to take into account. The main question you have to ask you

New committer: Jay Katariya

The Project Management Committee (PMC) for Apache Logging has invited Jay Katariya to become a committer and we are pleased to announce that he has accepted. Please join us in welcoming Jay to their new role and responsibility in our project community. Welcome to Log4Jay, Jay! ;-) Piotr On beha

Re: Create artifacts for optional features

Hi Gary, On 21.01.2025 13:46, Gary Gregory wrote: This all sounds very confusing to me. Using this scheme, I could create a set of dependencies on 2.x with empty jars that don't work on 3.x (because I picked the wrong jars). There is no way to verify that what I'm doing on 2.x will work on 3.x w

Re: Create artifacts for optional features

Hi Robert, On 19.01.2025 18:39, Robert Middleton wrote: If I'm understanding this correctly, this sounds like a bad idea. While it does make the 2.x -> 3.x transition easier, it creates a bigger issue for when you go from 2.x -> 2.y. As long as `x` is higher than `y` there will be no problems:

Re: Create artifacts for optional features

Hi Ralph, On 19.01.2025 17:55, Ralph Goers wrote: I must be misunderstanding. IIUC you are proposing that to eliminate optional dependencies we create a bunch of empty jars, presumably with a pom that has the dependency as required. How exactly does that help? Doesn’t that new, empty artifa

Create artifacts for optional features

Hi all, Maven is notably bad at handling optional dependencies, which are basically ignored by consumers of the POM file. While Log4j Core 3 solves this problem by not having **any** optional dependencies, we could backport this feature also to Log4j Core 2. What do you think about adding em

Re: Archiving Chainsaw and Flume GitHub repositories

Hi Volkan, On 15.01.2025 10:03, Volkan Yazıcı wrote: *I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub repositories. Objections?* +1 Could you also archive/remove the `2.3.x` and `2.12.x` web pages. As recent questions show, these are still used. Piotr

[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 th

[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: [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 < f384ad3659c6f2529dc5f3516d24e26092c74eca < fada7f734209587

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

Could you diff the `target/reference/org.apache.logging.log4j/log4j-bom-2.24.3-cyclonedx.xml` and `target/bom.xml` files instead, as in my previous e-mail? On Tue, Dec 10, 2024 at 8:52 AM Piotr P. Karwasz wrote: [ERROR] sha512 mismatch log4j-bom-2.24.3-cyclonedx.xml: investigate with diffo

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

Hi Gary, On 10.12.2024 13:26, Gary Gregory wrote: Using: mvn verify -Prelease artifact:compare -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 (Should' we also say "clean"?) I don't believe `clean` is necessary. I ran `mvnw verify artifact:compare` tw

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

Hi Gary, On 10.12.2024 13:23, Gary Gregory wrote: sh mvnw verify \ -Prelease artifact:compare \ -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be compromised. Investigate o

[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 Nexus

Re: Add JSpecify as `compile` dependency

Hi Gary, On 2.12.2024 20:28, Gary D. Gregory wrote: Just on the CP for one app tooling stack: org.jetbrains.annotations.NotNull org.jetbrains.annotations.Nullable com.sun.istack.NotNull com.sun.istack.Nullable org.springframework.lang.NonNull org.springframework.lang.Nullable jakarta.annotation

Re: PMC Meeting in December

Hi Ralph, On 1.12.2024 22:09, Ralph Goers wrote: Do you two have jobs lined up? I’m curious what you will be doing. Volkan already started a new job in November. My current plan is to continue consulting on software supply chain security, software modularization and logging. The ulterior mot

PMC Meeting in December

Hi all, I think we should have a PMC meeting in December to summarize what we achieved in 2024. How does Sunday, 15th sound? A rapid draft of the agenda might be: * Status of Log4cxx. * Status of Log4net. * Status of Log4j and future plans. Note that starting January 2025, neither Volkan n

Re: [RESULT][VOTE] Release Apache Log4cxx 1.3.1

Hi Stephen, On 1.12.2024 02:16, Stephen Webb wrote: With that the vote passed with 3 +1 votes from Jan Friedrich, Piotr P. Karwasz, Robert Middleton and myself. The vote passed with 4 +1 votes. ;-) I am happy to see that each recent Log4cxx and Log4net releases, has a vote from each one of

Re: [VOTE] Release Apache Log4cxx 1.3.1

Hi Stephen, On 28.11.2024 01:14, Stephen Webb wrote: This is a vote to release the Apache Log4cxx 1.3.1. Website:https://logging.staged.apache.org/log4cxx/1.3.1/changelog.html GitHub:https://github.com/apache/logging-log4cxx Commit: 4d22bb0 Distribution:https://dist.apache.org/repos/dist/dev/lo

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: Problems creating custom appender using JPMS service in 3.0.0-beta3

Hi Pavel, [NOTE: I am cross-posting this to `dev@logging`, since I believe it is more appropriate there] On 29.11.2024 10:26, PavelTurk wrote: In the world of JPMS, there’s a service, we implement it, and we add it. I haven’t heard of a service + PROCESSOR that needs to be used. Can you poin

Re: Disable JIRA issue creation

Hi all, On 14.10.2024 12:12, Piotr P. Karwasz wrote: What do you think about disabling the creation of new JIRA issues for LOG4J2? I confirmed with INFRA that this is technically possible. Disabling new issues would prevent JIRA users from filing new reports against LOG4J2. Personally I look at

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 fea

Re: Cleanup of `downloads.apache.org`

Hi Gary, On 16.11.2024 19:42, Gary Gregory wrote: Note that the statement on the EOL site is incorrect: "The reload4j project provides a drop-in replacement for Log4j 1.x with maintenance and security fixes." It certainly is not a "drop-in replacement" because it ripped out public classes and

Re: A logger config named "root"

Hi Gary, On 19.11.2024 19:47, Gary D. Gregory wrote: I don't want to not loose support for "root" (lower-case) in the Log4j 1 configuration properties bridge since that's a documented feature in 1.x. I still have a product that uses 1.x style properties files, and converting converting our ins

Add JSpecify as `compile` dependency

Hi all, On 19.10.2024 09:28, Piotr P. Karwasz wrote: PS: Regarding annotations, can you take a look at issue #3110[4]. Users are regularly reporting issues for annotations with a `provided` scope. This is due to the `classfile` option to `-Xlint`, which basically only covers missing annotations

[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 th

[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

Re: A logger config named "root"

Hi Gary, On 19.11.2024 17:50, Gary D. Gregory wrote: It seems odd to have a logger name not supported in a configuration file but then support it programmatically. Did I misread your suggestion? If that's the case, then issuing a warning makes even more sense. The `error` alias works perfect

A logger config named "root"

Hi all, In Log4j Core 2 there is a residual support for a logger named "root", e.g.: has the same effect as: However `Configurator.setLevel()`, `Configuration.getLoggerConfig()` and other methods don't support the `root` alias. Should we introduce support for `root` to those methods or ra

Re: A logger config named "root"

Hi Gary, On 19.11.2024 13:08, Gary Gregory wrote: This seems like a nice clean up that will break a lot of configurations. How about we issue a warning in 2.x like "The logger name 'root' is deprecated and will be removed in 3.0"? I thought about going in the other direction: allow users to c

[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

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

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://dist.apache.org/repos/dist/dev/logging/log4j/2.24.2 Nexus

Re: Log4j release 2.24.1

Hi Gary, On 16.11.2024 17:41, Gary Gregory wrote: [1]https://github.com/apache/logging-log4j2/issues/3143 This issue points to the merged PR https://github.com/apache/logging-log4j2/pull/2936, a large change set with zero tests. This isn't great since there are no tests to catch regressions :-(

Log4j release 2.24.1

Hi all, Due to bug #3143[1], which allows a `Logger` to be garbage-collected before it is returned by `LoggerContext#getLogger()`, I am planning a 2.24.2 release with just two changes: * A fix for the above mentioned bug (see PR #3209[2]). * A fix for a bug related to `ThreadContextMap` (see

Re: Cleanup of `downloads.apache.org`

Hi Ralph, On 14.11.2024 06:50, Ralph Goers wrote: Log4j 2.3.x and 2.12.x don’t need votes. We declared that we were no longer supporting Java 6 and then Java 7 and that those would be the last releases to do so. We made an exception for Log4Shell and created patches for both since the securit

Re: Compatibility between Log4j API and implementation

Hi PJ, On 14.11.2024 21:29, PJ Fanning wrote: The problem with log4j-api 2.24.1 is it can return null Logger instances when used with log4j-core 2.24.0 leading to NullPointerExceptions. That is a bug in `log4j-api` 2.24.1 and it should affect both users of `log4j-core` 2.24.0 and 2.24.1. The

Compatibility between Log4j API and implementation

Hi all, We usually recommend users to have a perfect version alignment between `log4j-api` and `log4j-core`. As reported by Dominik in [1], users of Apache POI and other libraries that use Log4j API, often end up with mismatched versions. The reason behind this is simple: `log4j-api` is a **t

Cleanup of `downloads.apache.org`

Hi all, Looking at our releases, as the appear on `projects.apache.org`[1], I think that it is about time to clean up `downloads.apache.org`. I would propose to: 1. Formally vote on the end-of-life of the Apache Extras for Apache log4j[2] and Apache log4php[3] projects. 2. Formally vote on

Re: Cleanup of `downloads.apache.org`

Hi Volkan, On 13.11.2024 16:54, Volkan Yazıcı wrote: On Wed, Nov 13, 2024 at 4:38 PM Piotr P. Karwasz wrote: 6. Currently we place all sub-projects of Log4j directly in the `logging` folder, but `archive.apache.org`[6] shows that it wasn't always this way. For example `log4j-scala` us

Re: Board report for November

Hi Gary, On 12.11.2024 12:49, Gary Gregory wrote: If we are going to mention components, shouldn't we also list Chainsaw? I could mention that the report concerns sub-projects that were active at the time of the last report. Log4php is also still in the dormant phase, although we should pro

Board report for November

Hi all, Sorry for the short notice, but only today I found the time to prepare the board report for November. Unless there are some remarks, I plan to send the following report before tomorrow's deadline. Summary: - Flume is dormant. Due to INFRA-26201[1], I am a little bit afraid to upda

[ANNOUNCE] Apache Log4j `3.0.0-beta3` released

The Apache Log4j team is pleased to announce the `3.0.0-beta3` 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.) s

[RESULT][VOTE] Release Apache Log4j `3.0.0-beta3` (RC1)

Hi all, On 9.11.2024 07:09, Piotr P. Karwasz wrote: This is a vote to release the Apache Log4j `3.0.0-beta3`. Website: https://logging.staged.apache.org/log4j/3.0.0-beta3/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: 28117e55f69892d3454672f9399e53fb7b74a321 Distribution

Flaky Rolling Appender tests

Hi Gary, On 9.11.2024 14:11, Gary Gregory wrote: I get this failure: [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.963 s <<< FAILURE! -- in org.apache.logging.log4j.core.appender.rolling.RollingAppenderDirectCronTest [ERROR] org.apache.logging.log4j.core.appender.rol

[VOTE] Release Apache Log4j `3.0.0-beta3` (RC1)

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

[DISCUSS][RESULT][VOTE] Release Apache Log4net 3.0.3

Hi Jan, On 7.11.2024 21:55, Jan Friedrich wrote: With that the vote passed with 4 +1 votes from Stephen Webb, Davyd McColl, Piotr P. Karwasz and myself. I will continue the release process. Davyd's +1 never made it to the mailing list. Are we having delivery problems again? Piotr

Re: [VOTE] Release Apache Log4net 3.0.3

Hi Jan, On 4.11.2024 19:23, Jan Friedrich wrote: 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 w

Re: Bridges in 2.x and 3.x

Gary, On 25.10.2024 08:19, Ralph Goers wrote: With the changes that have been made the bridges only have a dependency on Logj4 API - which is only in the 2.x branch. Should these artifacts only be on the 2.x branch as well? These bridges don’t change nearly as often as core or even api do. IM

Re: New API for log level manipulation

Hi Gary, On 3.11.2024 13:23, Gary Gregory wrote: On Sat, Nov 2, 2024 at 11:15 PM Ralph Goers wrote: I think you missed my point. I don’t think Log4j-core, Logback or whatever should need to implement anything. The point of such an API is to provide a standard API that implements whatever is ne

Re: New API for log level manipulation

Hi Gary, On 2.11.2024 23:14, Gary D. Gregory wrote: In general, talking about API signatures without (pseudo)-Javadoc is not great, there is too much wrong for miscommunication or plain old guesing. FWIW, the JavaDoc is there in my repo[1] together with a short README[2]. I only removed it to

Re: New API for log level manipulation

Hi Ralph, On 2.11.2024 22:48, Ralph Goers wrote: 1. getLoggerContext returns a meaningless object. The object returned only has value if you know what it is and if you do then you might as well be tied to whatever the implementation is. 2. You are passing in an arbitrary parameter to getInstan

Re: New API for log level manipulation

Hi all, On 31.10.2024 16:11, Piotr P. Karwasz wrote: Currently we have `o.a.l.l.c.config.Configurator` that allows level manipulation, but this is a Log4j Core specific class, which only works with Log4j Core. We could publish a small API (e.g. called LogAdmin) that allows to: * list the

Re: New API for log level manipulation

Hi Gary, On 31.10.2024 17:12, Gary Gregory wrote: set the configured level of a single logger Some people (like me) will want to enable debug all in one go for example, even for loggers that have not been instantiated yet. I think we should distinguish whether this is set the level for a hie

New API for log level manipulation

Hi all, In last few days I have encountered the problem of retrieving and setting the configured level of a logger twice (in Nashorn[1] and Apache Kafka[2]). What do you think about introducing a public API to do this sort of things in an implementation independent way? Currently we have `o.

Re: [VOTE] Release Apache Log4j Transformation Tools `0.2.0`

Hi Ralph, On 27.10.2024 07:32, Ralph Goers wrote: This is a vote to release the Apache Log4j Transformation Tools `0.2.0`. Website: https://logging.staged.apache.org/log4j/transform-0.2.0 GitHub: https://github.com/apache/logging-log4j-transform Commit: 074f4c67d0514c52eb52a0139d0086b20d60d25c

Re: Bridges in 2.x and 3.x

Hi Gary, On 23.10.2024 12:50, Gary D. Gregory wrote: Another batch of repositories? -1 and you must be joking. We really are going off the map here IMO :( Releasing different jars from one repo is the same as releasing jars from one SSD: A repo is just a folder with subfolders you can organiz

Multi-repository deploy workflows

Hi all, To reassure those that fear that splitting components over multiple repos can make integration between Log4j components more difficult, I have submitted a couple of PRs last week to simplify that: * I have introduced a new reproducibility check in apache/logging-parent#271[1] and apache/l

Re: Bridges in 2.x and 3.x

Hi Gary, On Wed, 23 Oct 2024 at 13:11, Gary D. Gregory wrote: > - `jul-to-log4j-core`: I understand that name as: The JUL API is implemented > in terms of Log4j's own impl guts. The difference with `jul-to-log4j-api` is > that we directly implement JUL? Without going though log4j-api? If that's

Re: Bridges in 2.x and 3.x

Hi Gary, On Wed, 23 Oct 2024 at 12:51, Gary D. Gregory wrote: > Releasing different jars from one repo is the same as releasing jars from one > SSD: A repo is just a folder with subfolders you can organize as you best see > fit. So why have 10 repos? Or how ever many we have now splintered Log4

  1   2   3   4   5   6   7   >