You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ppkarwasz (via GitHub)" <gi...@apache.org> on 2024/11/04 08:54:19 UTC
[I] Synchronization with `main` backlog (logging-log4j2)
ppkarwasz opened a new issue, #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161
This meta-issue lists the PRs or modifications that didn't make it to `main` yet. Feel free to modify it after each merged PR that you don't have time or can not port immediately:
- [ ] #2962
- [ ] #3010
- [ ] #3055
- [ ] #3052
- [ ] https://github.com/apache/logging-log4j2/commit/7683460816162257a6bff258fd8941d4a2604b14
- [ ] #3092
- [ ] #3118
- [ ] #3158
- [ ] #3133
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3284877015
The changes to `InternalLoggerRegistry` were added to `2.x` in #3681. They didn't end up in `main` as far as I know, though.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ashr123 (via GitHub)" <gi...@apache.org>.
ashr123 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3649225990
hey @ppkarwasz, what about #3789?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3297219023
> Both those PRs are already merged, so:
>
> * First [Removes weak references from `LoggerRepository` #3199](https://github.com/apache/logging-log4j2/pull/3199) needs to be cherry picked, because it introduces `InternalLoggerRegistry`.
> * Then [Expunge stale entries in InternalLoggerRegistry #3681](https://github.com/apache/logging-log4j2/pull/3681) needs to be cherry picked.
>
> Of course, this can be done in one PR. Since `main` does not host the Log4j API any more, parts of those PR need to be simply discarded.
so can I skip and take some other
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-5670383958
I started this, so I'll finish it.
In Q1 2024 we did a colossal boring work of synchronizing `2.x` and `main` and it would be a pity for those months to go to waste.
Today we have AI agents to do that work and I'll use both of them to find every last “Javadoc” commit that modifies a dot in one branch, but not the other or adds a useless `final` qualifier.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vy (via GitHub)" <gi...@apache.org>.
vy commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3271956955
> can I take pr [#3199](https://github.com/apache/logging-log4j2/pull/3199)
@ramanathan1504, go ahead. (AFAIK, @jvz is busy with DI- and plugins-related tasks.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3263848444
@jvz
PR #3381
issue #3170
synced with main, can I take pr #3199
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "jvz (via GitHub)" <gi...@apache.org>.
jvz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3289826155
I'm not actively working on other issues at the moment, but I am available for code review and to answer questions about how things work. @ramanathan1504
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vy (via GitHub)" <gi...@apache.org>.
vy commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3654527334
> what about #3789?
@ashr123, feel free to submit a PR porting #3789 from `2.x` to `main`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3271959775
@vy
ok
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ashr123 (via GitHub)" <gi...@apache.org>.
ashr123 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-5670443800
I don’t know what did you mean exactly, but I don’t think it’s useless (the `private`/`final`/`static` parts)… the JVM can do heuristics on those so the machine code can be more efficient with little to no effort on our side..
just saying 🙂
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vy (via GitHub)" <gi...@apache.org>.
vy commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3675961889
> > [@ashr123](https://github.com/ashr123), feel free to submit a PR porting [#3789](https://github.com/apache/logging-log4j2/pull/3789) from `2.x` to `main`.
>
> As I can see, all the patterns (except of `org.apache.logging.log4j.core.pattern.DatePatternConverter#DEFAULT_PATTERN`) dropped… so.. I’m not sure my PR is relevant anymore, correct me if I’m wrong..
@ashr123, my mistake – I've jumped to gun too quick.
> If we were to provide predefined options...
@ppkarwasz, I think there are more pressing issues blocking `3.0.0` – let's focus on them first. We can always discuss introducing named date & time patterns to Log4j 3 at a later time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3220296113
@vy
Thanks for the guidance! I’ll begin with the smaller issues to get familiar with the codebase and then tackle the more complex ones.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3218605987
Hi @ppkarwasz, I’d like to help with porting some of the changes listed here from 2.x to main.
I’m planning to start with:
• [ ] Remove outdated @BaselineIgnore annotations (#3133)
I’ll create separate PRs for each, referencing this issue. Please let me know if this approach works or if you’d prefer I prioritize other items.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3220568814
Hi @ramanathan1504,
Thank you for the help. Please coordinate with @jvz, since he is also working on these ports.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3283742137
Hi @vy,
While working on this PR I noticed that the failing tests are related to earlier work in PR #3418 (issues #3252, #3399, and the discussion in #3209). That some change seems to have landed in the 2.24 branch, but I don’t see it yet in 2.x or main.
Am I correct that the fix needs to be ported forward (from 2.24 → 2.x → main) before this PR can pass cleanly?
Would you like me to take care of the porting as part of this PR (or as separate follow-ups), or should I rebase on a branch where the port has already been done?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vy (via GitHub)" <gi...@apache.org>.
vy commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-4973203950
@vpelikh, let me be brutally honest: I'm already getting grinded by triaging issues and reviewing fixes to `2.x`. I doubt if I can timely review your PRs. I will see if @ramanathan1504, our new Log4j committer, would want to give it a stab.
@ramanathan1504, I'll DM you.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3247976346
Hi @jvz, I noticed that PR #3381 fixed issue #3170 in the 2.x branch. Should this also be ported into main? If it’s not already in progress, I’d be happy to take it up.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3287469875
@ppkarwasz
so first #3681 needs to port then i will port #3199 and related pr's to main..right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vy (via GitHub)" <gi...@apache.org>.
vy commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3219563110
> I’d like to help with porting some of the changes listed here from 2.x to main.
@ramanathan1504, please be our guest in doing so. PR-per-issue is a good idea. I advise starting with simpler ones and making your way to more involved issues.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "vpelikh (via GitHub)" <gi...@apache.org>.
vpelikh commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-4810294014
Hi everyone,
I've been working on porting the PRs listed in this meta-issue to `main`. Here's what I've completed so far:
- [#3158](https://github.com/apache/logging-log4j2/pull/3158) → [#4152](https://github.com/apache/logging-log4j2/pull/4152)
- [#3226](https://github.com/apache/logging-log4j2/pull/3226) → [#4153](https://github.com/apache/logging-log4j2/pull/4153)
- [#3195](https://github.com/apache/logging-log4j2/pull/3195) → [#4154](https://github.com/apache/logging-log4j2/pull/4154)
- [#3265](https://github.com/apache/logging-log4j2/pull/3265) → [#4156](https://github.com/apache/logging-log4j2/pull/4156)
- [#3418](https://github.com/apache/logging-log4j2/pull/3418) → ported as part of [#4157](https://github.com/apache/logging-log4j2/pull/4157) (which also introduces `InternalLoggerRegistry` to `main`)
Now I'd like to clarify the status of the remaining items:
1. **#3217** and **#3381** – I think these might already be present in `main`, but could someone confirm if any additional porting work is still needed?
2. For the other PRs still mentioned in the description:
- #2716
- #2962
- #3583
- #3171
Could you please let me know their current status and how I can best help to move them forward? I'm ready to pick up any pending work.
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3297231668
> I'm not actively working on other issues at the moment, but I am available for code review and to answer questions about how things work. [@ramanathan1504](https://github.com/ramanathan1504)
Thanks! I’ll reach out if I have any questions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3297182983
Hi @jvz, thanks for your work on this.
I've merged the latest changes from the target branch, including #3681 and #3199, and I'm now encountering a build failure in the `log4j-kit` module.
The OSGi `bnd-maven-plugin` is failing during its processing step with the following errors:
```
[ERROR] /Users/ramanathan/Contributor/logging-log4j2/log4j-kit/.flattened-pom.xml [0:0]: Export org.apache.logging.log4j.kit.logger, has 1, private references [org.apache.logging.log4j.kit.recycler]
[ERROR] /Users/ramanathan/Contributor/logging-log4j2/log4j-kit/.flattened-pom.xml [0:0]: Export org.apache.logging.log4j.kit.recycler.support, has 1, private references [org.apache.logging.log4j.kit.recycler]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal biz.aQute.bnd:bnd-maven-plugin:7.1.0:bnd-process (generate-module-descriptors) on project log4j-kit: Errors in bnd processing, see log for details.
```
The issue is that two exported packages (`org.apache.logging.log4j.kit.logger` and `org.apache.logging.log4j.kit.recycler.support`) have public APIs that expose types from `org.apache.logging.log4j.kit.recycler`, which is currently not an exported (i.e., private) package. This violates module encapsulation rules.
To resolve this, I see two possible approaches:
* **Option 1: Promote `org.apache.logging.log4j.kit.recycler` to a Public Package.**
We can add this package to the `<Export-Package>` instruction in the `pom.xml`. This would make it an official part of the `log4j-kit` public API.
* **Option 2: Keep `org.apache.logging.log4j.kit.recycler` as an Internal Package.**
This would maintain stricter encapsulation. To fix the build, we would need to refactor the public APIs in the `logger` and `recycler.support` packages to avoid exposing types from `recycler`. This is often the preferred approach for internal utility packages.
Could you please provide guidance on which approach aligns better with the project's design goals? Is `recycler` intended to be a public utility, or should it remain an internal implementation detail?
Alternatively, if this has already been fixed in a different PR I might have missed, please let me know.
Once I have your feedback, I am happy to update the PR accordingly.
Thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3287608313
Both those PRs are already merged, so:
- First #3199 needs to be cherry picked, because it introduces `InternalLoggerRegistry`.
- Then #3681 needs to be cherry picked.
Of course, this can be done in one PR. Since `main` does not host the Log4j API any more, parts of those PR need to be simply discarded.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-4815434618
> Hi everyone,
>
> I've been working on porting the PRs listed in this meta-issue to `main`. Here's what I've completed so far:
>
> * [#3158](https://github.com/apache/logging-log4j2/pull/3158) → [#4152](https://github.com/apache/logging-log4j2/pull/4152)
>
> * [#3226](https://github.com/apache/logging-log4j2/pull/3226) → [#4153](https://github.com/apache/logging-log4j2/pull/4153)
>
> * [#3195](https://github.com/apache/logging-log4j2/pull/3195) → [#4154](https://github.com/apache/logging-log4j2/pull/4154)
>
> * [#3265](https://github.com/apache/logging-log4j2/pull/3265) → [#4156](https://github.com/apache/logging-log4j2/pull/4156)
>
> * [#3418](https://github.com/apache/logging-log4j2/pull/3418) → ported as part of [#4157](https://github.com/apache/logging-log4j2/pull/4157) (which also introduces `InternalLoggerRegistry` to `main`)
>
>
> Now I'd like to clarify the status of the remaining items:
>
> 1. **[ Feat(SystemClock): Added PreciseClock implementation to the system clock class, for the benefit of Java 8 users. #3217](https://github.com/apache/logging-log4j2/pull/3217)** and **[Fix(Documentation): Fixed ConfigurationStrSubstitutor dccumenation. #3381](https://github.com/apache/logging-log4j2/pull/3381)** – I think these might already be present in `main`, but could someone confirm if any additional porting work is still needed?
>
> 2. For the other PRs still mentioned in the description:
>
> * [Revamp the `Extending`, `Plugins`, `Architecture`, and `Programmatic configuration` pages #2716](https://github.com/apache/logging-log4j2/pull/2716)
> * [Implement `MessageFactory`-namespaced logger registry (blocked by `2.24.1` release) #2962](https://github.com/apache/logging-log4j2/issues/2962)
> * [[main] Correct example property syntax for PatternMatch under ScriptP… #3583](https://github.com/apache/logging-log4j2/pull/3583)
> * [Improve implementations of `LogEvent.toImmutable()` and `ReusableMessage.memento()` #3171](https://github.com/apache/logging-log4j2/pull/3171)
>
> Could you please let me know their current status and how I can best help to move them forward? I'm ready to pick up any pending work.
>
>
> Thanks!
@vpelikh
Thanks for the contribution! The team is currently working on other issues, and what you’ve done is really helpful. Please be patient while the team reviews your PR. They’ll provide feedback and update you if any additional changes are needed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization between `2.x` and `main` [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-6012154418
## Port list
### W1. Bug fixes that apply cleanly (14)
**How:** port first; one small PR each, or a few per PR if they touch the same class.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `8d05a73372` | #3456 | 2025-03-01 | Fixed AbstractFilterable#isFiltered javadoc (#3300) | **untriaged** | clean |
| 2 | `2bc484c30d` | #3655 | 2025-05-19 | Handle missing stack traces in ExtendedThreadInformation | **untriaged** | clean |
| 3 | `78d4cb8ed3` | #3457 | 2025-05-25 | Fixed handling of null 'replacement' parameter in RegexReplacement#createRegexReplace | **untriaged** | clean |
| 4 | `6cd74a88ba` | #3802 | 2025-07-04 | fix: Disable sharing of formatted timestamps between threads | **untriaged** | clean |
| 5 | `b00133be81` | #3831 | 2025-07-20 | Correct log message format in `AbstractDriverManagerConnectionSource` | **untriaged** | clean |
| 6 | `286191e525` | #3851 | 2025-07-24 | DefaultLayout: Append a newline to the serialized LogEvent | **untriaged** | clean |
| 7 | `8e80e9e37a` | #3905 | 2025-09-02 | Fix the missing Error Prone version | **untriaged** | clean |
| 8 | `9b9a0d4350` | #3932 | 2025-09-18 | fix: parsing and merging of literals in `InstantPatternDynamicFormatter` | **untriaged** | clean |
| 9 | `7125d933cf` | #3934 | 2025-10-03 | Fix: prevent ThrowableStackTraceRenderer from throwing NPEs | **untriaged** | clean |
| 10 | `841efff2a9` | #4081 | 2026-05-21 | Improve `CronExpression` tests to cover daylight saving and scheduling logic | **untriaged** | clean |
| 11 | `33c8236d88` | #4217 | 2026-08-27 | docs: Routing Appender security considerations for high-cardinality keys | labelled | clean |
| 12 | `6bcc6811e9` | #4252 | 2026-09-17 | Honor spring.cloud.config.watch.enabled on Log4j2EventListener | labelled | clean |
| 13 | `2452ea5755` | #4229 | 2026-09-17 | do not apply POSIX file attributes through symbolic links | labelled | clean |
| 14 | `7326bebf87` | #4335 | 2026-09-19 | Guard %rEx{short.*} against an empty root-cause stack trace | labelled | clean |
### W2. Bug fixes with conflicts (25)
**How:** resolve by hand; keep `main`'s design and re-apply only the fix.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `caffa21f64` | #3212 | 2024-11-18 | Fix off-by-one in `StackTraceStringResolver` | **untriaged** | conflict: StackTraceStringResolverTest.java |
| 2 | `d8cbe77a0a` | #3502 | 2025-02-27 | Bugfix/log4 j 3359 2 | **untriaged** | conflict: CoreTypeConverters.java |
| 3 | `3da98f7c9d` | #3581 | 2025-04-01 | fix ShutdownDisabledTest and LoggerContext_shutdownDisable changelog | **untriaged** | conflict: ShutdownDisabledTest.java |
| 4 | `afa773a1ff` | #3450 | 2025-04-10 | Add transitive compileOnlyApi (requires static) dependencies | **untriaged** | conflict: pom.xml |
| 5 | `4a7ddf1dfb` | #3650 | 2025-05-08 | Prevent NPE with rootLogger shorthand when no appenders are specified | **untriaged** | conflict: LoggerConfig.java |
| 6 | `a3a4c6c16f` | #3763 | 2025-06-23 | Move `jspecify.version` property and `java8-tests` profile from `log4… | **untriaged** | conflict: pom.xml |
| 7 | `e08c7ba214` | #3785 | 2025-06-28 | fix: Define version of `error_prone_annotations` in parent POM | **untriaged** | conflict: pom.xml |
| 8 | `c5a1955789` | #3795 | 2025-07-04 | fix: Add `resource:` protocol to allowed URL schemes by default | **untriaged** | conflict: UrlConnectionFactory.java, properties-transport-security.adoc |
| 9 | `2f79c39696` | #3852 | 2025-08-04 | ConsoleAppender: Fix missing default Target value | **untriaged** | conflict: ConsoleAppender.java |
| 10 | `187f38cd89` | #3872 | 2025-09-01 | Round `initialTime` in `RollingFileManager` | **untriaged** | conflict: RollingFileManager.java |
| 11 | `59d2be98a4` | #3920 | 2025-09-18 | fix: recognize nested converters in `alwaysWriteExceptions` | **untriaged** | conflict: PatternParserTest.java |
| 12 | `c9a38ed754` | #3955 | 2025-10-20 | Fix `ArrayIndexOutOfBoundsException` in `ThrowableStackTraceRenderer` when the stack | **untriaged** | conflict: ThrowableInvertedStackTraceRenderer.java, ThrowablePatternConverterTest.java, ThrowableStackTraceRenderer.java |
| 13 | `3b93748497` | #4002 | 2025-12-15 | Fix host name verification in `SSLSocketManager` | **untriaged** | conflict: SslSocketManager.java |
| 14 | `752d023795` | #4008 | 2025-12-30 | Fix writeHeader computation in RollingRandomAccessFileManager | **untriaged** | conflict: RollingRandomAccessFileManager.java, RollingRandomAccessFileManagerTest.java |
| 15 | `878f951809` | #4072 | 2026-05-21 | Fix `createOnDemand` for Rolling File Appender | **untriaged** | conflict: RollingFileManager.java |
| 16 | `dec43515eb` | #4130 | 2026-06-11 | Document locale handling in the Pattern Layout date pattern converter | **untriaged** | conflict: pattern-layout.adoc |
| 17 | `f10c986684` | #4127 | 2026-06-15 | Fix resource leaks in `ConfigurationSource` when loading via URL | **untriaged** | conflict: ConfigurationSource.java |
| 18 | `de17f604c2` | #4118 | 2026-07-24 | Fix NPE in ConfigurationScheduler by ensuring scheduledFuture is chec… | labelled | conflict: ConfigurationScheduler.java |
| 19 | `abcb38f9cc` | #4245 | 2026-08-27 | fix: treat null parameters as empty in CsvParameterLayout | labelled | conflict: CsvParameterLayoutTest.java |
| 20 | `466f98f471` | #4049 | 2026-08-31 | Catch `LinkageError` in `ThrowableExtendedStackTraceRenderer#loadClass` (#4028) | labelled | conflict: TestFriendlyException.java |
| 21 | `9bcbf7e160` | #4303 | 2026-09-17 | Fix Pattern Layout's stack trace rendering for non-idempotent `Throwable::getCause` | labelled | conflict: TestFriendlyException.java, ThrowableStackTraceRenderer.java |
| 22 | `89db25a2b7` | #4259 | 2026-09-17 | Fix predefined ANSI styles in JAnsiTextRenderer | labelled | conflict: AnsiTextRenderer.java |
| 23 | `51f47051d6` | #4336 | 2026-09-21 | Grow DatagramOutputStream buffer and drop oversized UDP payloads | labelled | conflict: DatagramOutputStream.java |
| 24 | `bc90b767d1` | #4329 | 2026-09-24 | Preserve custom Configuration elements under CompositeConfiguration | labelled | conflict: AbstractConfiguration.java, package-info.java |
| 25 | `a9761b0de1` | #4355 | 2026-09-25 | `FileUtils.mkdir(File, boolean)` looses exception causes | labelled | conflict: FileUtils.java, FileUtilsTest.java |
### W3. Bug fixes whose files moved or are missing on `main` (17)
**How:** find the class's new home (module map in step 0), re-apply the fix there; if the code is gone, label the source PR `port-done` with the reason.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `43a0e29781` | #3247 | 2024-12-07 | Add a Jakarta JMS Appender #2295 | **untriaged** | conflict + moved: CONFLICT (modify/delete): .github/depend, CONFLICT (modify/delete): log4j-core/src, CONFLICT (modify/delete): src/site/antor, message-queue.adoc, package-info.j |
| 2 | `f5c6d73772` | #3398 | 2025-01-27 | Fix loading of the effective `RecyclerFactoryConverter` | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-layout-t |
| 3 | `3709962553` | #3645 | 2025-05-06 | Improve performance and avoid memory consumption if logging primitive arrays as param | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-api-test, CONFLICT (modify/delete): log4j-api/src/, ParameterFormatterBenchmark.java |
| 4 | `49cdf7457e` | #3675 | 2025-06-02 | StringMap: Generalize `equals`/`hashCode` across implementations | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-api/src/, package-info.java |
| 5 | `de63a4ff1e` | #3718 | 2025-06-20 | Correct script resolution order dependency | **untriaged** | conflict + moved: AbstractConfiguration.java, CONFLICT (modify/delete): log4j-core-tes |
| 6 | `9b663899eb` | #3773 | 2025-06-28 | fix: Restore Backward Compatibility with Spring Boot Reconfiguration | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core-tes, LoggerContext.java, ShutdownDisabledTest.java |
| 7 | `7da8450629` | #3797 | 2025-07-03 | fix: Fix Java type for annotated array parameters | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core-tes |
| 8 | `cab8ae8944` | #3800 | 2025-07-04 | fix: Add GraalVM reachability metadata for non-plugin class instantiations | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-api/src/, CONFLICT (modify/delete): log4j-core/src, CONFLICT (modify/delete): log4j-layout-t |
| 9 | `c41feeddad` | #3919 | 2025-09-12 | fix: make `%ex` behavior context-independent | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-taglib/s, LateConfigAbstractTest.xml, PatternParserTest.java |
| 10 | `9643c2220f` | #3953 | 2025-10-24 | Fix nullability issues in `SslConfiguration` | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core/src, CONFLICT (modify/delete): log4j-jakarta-, SslConfiguration.java, SslSocketManager.java, UrlConnectionFactory.java |
| 11 | `37a03838eb` | #3996 | 2025-12-15 | Use binary names in `GraalVmProcessor` | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core-tes |
| 12 | `359ee520e3` | #4155 | 2026-07-26 | Revamp XML configuration testing and documentation | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core-tes, XmlConfiguration.java |
| 13 | `9f3b57983e` | #4249 | 2026-09-02 | Fix circular references in exceptions | labelled | conflict + moved: CONFLICT (modify/delete): log4j-jpa/src/, NoSqlDatabaseManager.java, ThrowablePatternConverterTest.java |
| 14 | `c685326e6d` | #4070 | 2026-09-02 | Deprecate externalContext and migrate to Map-backed getObject/putObject | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-api/src/, CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-jakarta-, CONFLICT (modify/delete): log4j-we |
| 15 | `e32663a474` | #4246 | 2026-09-14 | fix: skip writes and still shut down after failed DB manager startup | labelled | conflict + moved: AbstractDatabaseAppenderTest.java, AbstractDatabaseManager.java, CONFLICT (modify/delete): log4j-cassandr |
| 16 | `4d49b758e7` | #4340 | 2026-09-23 | Compute AsyncLogger location when the caller passes null | labelled | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core/src |
| 17 | `e076aa5f23` | #4280 | 2026-10-01 | Restore UNCACHED thread name updates in AsyncLogger | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core/src |
### W4. Docs and tests that apply cleanly (11)
**How:** port; one docs PR can carry several.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `cb9fc92284` | #3012 | 2024-09-25 | Fix document mistake for `log4j-jpl` | **untriaged** | clean |
| 2 | `070e1a82bf` | #3051 | 2024-10-03 | Fix LowerLookup code link | **untriaged** | clean |
| 3 | `b1b0143608` | #3092 | 2024-10-16 | Correct example property syntax under ScriptPatternSelector | labelled | clean |
| 4 | `52ca6a352c` | #3768 | 2025-06-28 | Fix UuidPatternConverter javadoc/adoc | **untriaged** | clean |
| 5 | `61ec36abd4` | #3854 | 2025-07-23 | Specify the scale (seconds) of the monitorInterval configuration integer | **untriaged** | clean |
| 6 | `7209b27ba4` | #3918 | 2025-09-12 | doc: clarify `%ex` whitespace behavior across versions | **untriaged** | clean |
| 7 | `296d1d7c3d` | #3983 | 2025-11-10 | Fix BurstFilter documentation regarding the level parameter | **untriaged** | clean |
| 8 | `2a15414e83` | #4062 | 2026-05-02 | Add documentation for third-party appenders and async HTTP appender specifically | **untriaged** | clean |
| 9 | `82432570e8` | #4042 | 2026-05-02 | Add documentation for `MessageRewritePolicy` | **untriaged** | clean |
| 10 | `a4364da103` | #4257 | 2026-08-27 | Fix date format from `mm` to `MM` in Pattern Layout docs | labelled | clean |
| 11 | `c2d3d84d3e` | #4320 | 2026-09-23 | Document the JdbcAppender truncateStrings attribute | labelled | clean |
### W5. Docs and tests with conflicts or moved files (24)
**How:** port the docs that describe 3.x behaviour; skip 2.x-only wording.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `ab85d1a62c` | #3010 | 2024-09-24 | Fix typos | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core/src, CONFLICT (modify/delete): log4j-jul/src/ |
| 2 | `ab0fdbc517` | #3054 | 2024-10-09 | Document GraalVM usage with Log4j | **untriaged** | conflict: installation.adoc, plugins.adoc |
| 3 | `2d61fe0e6a` | #3069 | 2024-10-10 | Upgrades JUnit to version `5.11.2` | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-api-test, LegacyLoggerContextSource.java, Log4jTest.java, LoggerContextSource.java, Ordered.java, package-info.java, pom.xml |
| 4 | `5afb86cc5f` | #3186 | 2024-11-08 | Fix code typo in the thread context docs | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): src/site/antor |
| 5 | `82184237ee` | #3174 | 2024-11-17 | Add missing setter in builder classes | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-core/src, StringMatchFilter.java, StringMatchFilterTest.java, package-info.java |
| 6 | `ed87354de1` | #3290 | 2024-12-15 | fix Figure 10 | **untriaged** | conflict: architecture.adoc |
| 7 | `c59fdd4a0e` | #3448 | 2025-02-10 | Fix log4j2.properties sample | **untriaged** | conflict: installation.adoc |
| 8 | `23290e480d` | #3525 | 2025-03-05 | Update refed Shadow plugin link | **untriaged** | conflict: faq.adoc |
| 9 | `6fd9c621ab` | #3677 | 2025-06-03 | Improve development-related documentation | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): .github/pull_r |
| 10 | `d5899c8906` | #3762 | 2025-06-21 | Pin `spotbugs-annotations` version to `4.8.6` | **untriaged** | conflict + moved: CONFLICT (modify/delete): .github/depend, pom.xml |
| 11 | `c4df56e979` | #3786 | 2025-07-03 | doc: Clarify and enhance `GraalVmProcessor` configuration example | **untriaged** | conflict: plugins.adoc |
| 12 | `1758179ef0` | #3944 | 2025-10-13 | Replace fixed delay with polling in `SyslogAppenderCustomLayoutTest` | **untriaged** | conflict: SyslogAppenderTestBase.java |
| 13 | `60c62ee8fd` | #3946 | 2025-10-22 | Stabilize `RollingAppenderDirectCronTest` and `XmlCompleteFileAppenderTest` | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core-tes |
| 14 | `141a54e987` | #3957 | 2025-10-24 | Stabilize `RollingAppenderDeleteAccumulatedCount1Test` | **untriaged** | conflict: RollingAppenderDeleteAccumulatedCount1Test.java |
| 15 | `e2234cf3c8` | #3967 | 2025-10-31 | Fix spelling | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-core/src |
| 16 | `1cfcda9b4c` | #3982 | 2025-11-07 | Add documentation for third-party filters and routing filter specifically | **untriaged** | conflict: filters.adoc |
| 17 | `9c22ca26d8` | #4006 | 2025-12-17 | docs: recommend use of appropriately scoped trust roots | **untriaged** | conflict: properties-transport-security.adoc |
| 18 | `8abfdfc142` | #3341 | 2025-12-29 | Add versioning and support policy information | **untriaged** | conflict: download.adoc |
| 19 | `c8a942155b` | #4025 | 2026-01-21 | Remove Log4j Jakarta EE link from navigation file | **untriaged** | conflict: nav.adoc |
| 20 | `4f474b3275` | #4030 | 2026-01-22 | Remove mentions of Log4j Scala | **untriaged** | conflict: api.adoc, log4j-features.adoc, nav.adoc |
| 21 | `8e7d897c85` | #4038 | 2026-03-02 | Fix the `AsyncLoggerConfig` ring buffer size property name in the manual | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): src/site/antor |
| 22 | `0f7f2c757f` | #4041 | 2026-03-16 | Avoid referring to `PluginBuilderAttribute.class` in `PluginProcessor` | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core/src |
| 23 | `acac6dd39c` | #4170 | 2026-07-26 | Align NOTICE files and drop redundant LICENSE resources | labelled | conflict: CONFLICT (add/add): Merge conflict in lo, NOTICE.txt |
| 24 | `6ad11e4003` | #4317 | 2026-09-16 | Fix the log4j-spring-cloud-config-client test harness | labelled | conflict: Log4j2EventListenerTest.java |
### W6. `changed`: decide one by one (17)
**How:** port if it is a bug fix; otherwise move the decision to beta5.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `328dd30bfb` | #3149 | 2024-10-31 | Prefix stack traces with a newline in Status Logger | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-api/src/ |
| 2 | `7f81b510d6` | #3217 | 2025-01-13 | Feat(SystemClock): Added PreciseClock implementation to the system clock class, for | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core-jav, CONFLICT (modify/delete): log4j-core/src, CONFLICT (rename/delete): log4j-core-jav, SystemMillisClock.java, package-in |
| 3 | `dc6c53ab7b` | #3171 | 2025-05-16 | Improve implementations of `LogEvent.toImmutable()` and `ReusableMessage.memento()` | **untriaged** | conflict + moved: AsyncLoggerConfigDisruptor.java, BlockingAppender.java, CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-api/src/, CONFLICT (modify/del |
| 4 | `138404a4fd` | #3454 | 2025-05-25 | Only set default configuration name if none has been previously set (… | **untriaged** | conflict: AbstractConfiguration.java |
| 5 | `14505330c1` | #3691 | 2025-06-20 | Enforce explicit names for global scripts and refine script id handling | **untriaged** | conflict: ScriptManager.java, ScriptRef.java, ScriptsPlugin.java, package-info.java |
| 6 | `f93b6b19db` | #3772 | 2025-06-28 | fix: Make `GraalVmProcessor` Arguments Optional | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-core-tes |
| 7 | `e9556bb8f6` | #3939 | 2025-10-10 | Optimize DefaultThreadContextMap.getCopy() performance | **untriaged** | files moved/missing on `main`: CONFLICT (modify/delete): log4j-api-test, CONFLICT (modify/delete): log4j-api/src/ |
| 8 | `4b7065b8b3` | #3968 | 2025-11-11 | Simplify file manager registry factory pattern | **untriaged** | conflict: FileManager.java, MemoryMappedFileManager.java, RandomAccessFileManager.java, RollingFileManager.java, RollingRandomAccessFileManager.java |
| 9 | `d46918c9e3` | #4033 | 2026-03-05 | Take `Throwable#toString()` into account while rendering stack traces in Pattern Layo | **untriaged** | clean |
| 10 | `d026d3f8d4` | #4111 | 2026-05-21 | Revamped `ListAppender` for thread-safety | **untriaged** | conflict: ListAppender.java |
| 11 | `019a92865a` | #4133 | 2026-06-11 | Fix stack trace rendering for exceptions with identity malfunction | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core/src, ThrowableStackTraceRenderer.java |
| 12 | `bf873ae58e` | #4228 | 2026-08-14 | Extend plugin processor message filtering and add [Log4j] prefixes | labelled | conflict + moved: CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-core/src, GraalVmProcessor.java, plugins.adoc |
| 13 | `d1f9355a55` | #4226 | 2026-08-31 | Fix startup delay and direct write file naming in CronTriggeringPolicy | labelled | conflict: CronExpressionTest.java, CronTriggeringPolicy.java, CronTriggeringPolicyTest.java |
| 14 | `4606de451b` | #4116 | 2026-09-02 | Fix handling of `onMatch` and `onMismatch` attributes in the properties configuration | **untriaged** | conflict + moved: BuiltConfiguration.java, CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-core-fuz, CONFLICT (modify/delete): log4j-core-tes, CONFLICT |
| 15 | `7f32b34008` | #4256 | 2026-09-26 | Switch the default minimum allowed plugin processor message severity from NOTE to ERR | labelled | conflict + moved: CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-core/src, GraalVmProcessor.java, plugins.adoc |
| 16 | `9cb17cf7b7` | #4271 | 2026-09-30 | Serialize the `LogEvent` message without `MarshalledObject` | **untriaged** | conflict + moved: CONFLICT (directory rename split): Uncle, CONFLICT (file location): log4j-api-test, CONFLICT (modify/delete): log4j-api-test, CONFLICT (modify/delete): log4j-ap |
| 17 | `5b89c4dcbe` | #4270 | 2026-09-30 | Apply the deserialization filter in test helpers on Java 9+ | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-api-test, CONFLICT (modify/delete): log4j-core-tes, Log4jLogEventTest.java, LoggerCont |
### D. `added`, `deprecated`, `removed`: **not beta4** (14)
**How:** beta5 / 3.1 decision; on `main`, replace a deprecated thing instead of porting the deprecation.
| # | 2.x commit | PR | Merged on 2.x | Title | Port label | Dry run vs `main` (2026-10-04) |
|---|---|---|---|---|---|---|
| 1 | `20035c443e` | #3199 | 2024-11-15 | Removes weak references from `LoggerRepository` | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-api/src/, CONFLICT (modify/delete): log4j-taglib/s, CONFLICT (modify/delete): log4j-to-jul/s, CONFLICT (modify/delete): log4j-to |
| 2 | `b23e9a56a9` | #3508 | 2025-03-21 | Fix shutdownDisable not taking effect(#2614) | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-spring-b, LoggerContext.java, ShutdownDisabledTest.java |
| 3 | `c299479b03` | #3703 | 2025-06-02 | Add option to provide URIs to monitor in addition to the config file | **untriaged** | conflict + moved: AbstractConfiguration.java, CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-core/src, package-info.java |
| 4 | `d6fe40d79a` | #3756 | 2025-06-26 | Deprecate withers in 2.x in favor of setters | **untriaged** | conflict + moved: AbstractAppender.java, AbstractFileAppender.java, AppenderSet.java, CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-core-tes, CONFLICT |
| 5 | `a6cb7b711c` | #3921 | 2025-10-29 | Add new `ConfigurationFactory::getConfiguration` accepting multiple URIs | **untriaged** | conflict: ConfigurationFactory.java, ConfigurationFactoryTest.java, package-info.java |
| 6 | `c5396fc4d5` | #4060 | 2026-03-16 | Add debug logs for successful resource loading in `Loader` | **untriaged** | clean |
| 7 | `1fdfe142d5` | #4063 | 2026-03-17 | Allow severity-based log message filtering in `PluginProcessor` | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-core/src, plugins.adoc |
| 8 | `d0c00e953a` | #4076 | 2026-04-19 | Add missing setters to `Rfc5424LayoutBuilder` | **untriaged** | conflict: Rfc5424Layout.java |
| 9 | `446d2baa20` | #4071 | 2026-05-28 | Add support for max compression delay in compression actions | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-core/src, DefaultRolloverStrategy.java, package-info.java |
| 10 | `2ca8348810` | #4119 | 2026-06-11 | Remove the `patternFlags` attribute from `RegexFilter` | **untriaged** | conflict: AbstractFilterableTest.java, Builder.java, RegexFilter.java, RegexFilterTest.java, package-info.java |
| 11 | `7775e125ae` | #4165 | 2026-07-01 | Adds `maxRandomDelay` configure to Rolling Appenders | **untriaged** | conflict + moved: AbstractAction.java, CONFLICT (modify/delete): log4j-core-tes, CONFLICT (modify/delete): log4j-core/src, DefaultRolloverStrategy.java, RollingAppenderDirectCron |
| 12 | `b6ba7d0af6` | #4171 | 2026-07-06 | Add native tracing fields to LogEvent to eliminate async MDC overhead | labelled | conflict: CONFLICT (directory rename split): Uncle, Log4jLogEvent.java, Log4jLogEventTest.java, MutableLogEvent.java, MutableLogEventTest.java, RingBufferLogEvent.java, R |
| 13 | `e8f7ec059a` | #4186 | 2026-09-11 | Add literal Context Data (MDC) filtering to JSON Template Layout | labelled | conflict: ReadOnlyStringMapResolver.java, pom.xml |
| 14 | `d2a8a11129` | #4365 | 2026-09-30 | Apply the outer `ObjectInputFilter` to nested streams | **untriaged** | conflict + moved: CONFLICT (modify/delete): log4j-1.2-api/, CONFLICT (modify/delete): log4j-api-test, CONFLICT (modify/delete): log4j-api/src/, CONFLICT (modify/delete): log4j-co |
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ramanathan1504 (via GitHub)" <gi...@apache.org>.
ramanathan1504 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3247949921
@ppkarwasz
ok
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "jvz (via GitHub)" <gi...@apache.org>.
jvz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3249999878
@ramanathan1504 go for it!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ashr123 (via GitHub)" <gi...@apache.org>.
ashr123 commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3656520900
> > what about [#3789](https://github.com/apache/logging-log4j2/pull/3789)?
>
> [@ashr123](https://github.com/ashr123), feel free to submit a PR porting [#3789](https://github.com/apache/logging-log4j2/pull/3789) from `2.x` to `main`.
As I can see, all the patterns (except of `org.apache.logging.log4j.core.pattern.DatePatternConverter#DEFAULT_PATTERN`) dropped… so.. I’m not sure my PR is relevant anymore, correct me if I’m wrong..
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization with `main` backlog [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-3664391139
Yes, in `main` there are no longer any predefined date/time patterns.
Based on real-world usage I have observed, most users tend to define their own preferred timestamp format. As a result, predefined patterns add maintenance cost without delivering much value, since they are rarely used as-is.
One possible exception we might consider is [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339), which provides a well-defined, timezone-aware, and widely recognized format. It could serve as a reasonable and safe default.
If we were to provide predefined options, I could imagine limiting them to a small, RFC 3339-based set, for example:
* **RFC 3339 `date-time`**: suitable for generic log output
* **RFC 3339 `full-date`**: useful for `filePattern` in rolling appenders
* **RFC 3339 `full-time`**: potentially useful when the date is already encoded in the file name (assuming rolling appenders preserve it correctly)
Rather than exposing these as implicit pattern shortcuts, I think it would be cleaner to define them as explicit Log4j plugins, similar to how the predefined color converters (`%black`, `%blue`, etc.) are implemented today. These plugins should probably default to UTC to avoid ambiguity.
Beyond this, I don’t see much value in additional predefined patterns. In practice, they often lead to locale-specific or timezone-less timestamps, which make it difficult to debug issues, especially around DST transitions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Synchronization between `2.x` and `main` [logging-log4j2]
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #3161:
URL: https://github.com/apache/logging-log4j2/issues/3161#issuecomment-5672163708
Sorry, this was a project-private joke.
When we synchronized `2.x` and `main`, we realized that many files differed only by the Javadoc or `final` qualifiers on a **local** variable. Before we started looking for differences, we had to agree on a deterministic formatter (Palantir Java formatter) and run an OpenRewrite rule to add `final` everywhere possible, which was easier than removing them in places when they are not useful.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org