github-actions[bot] commented on issue #3579:
URL:
https://github.com/apache/logging-log4j2/issues/3579#issuecomment-2910906538
This issue is stale because it has been waiting for your feedback for more
than 60 days. The Apache Logging Services community values every submitted
issue, but w
github-actions[bot] commented on issue #3577:
URL:
https://github.com/apache/logging-log4j2/issues/3577#issuecomment-2910906574
This issue is stale because it has been waiting for your feedback for more
than 60 days. The Apache Logging Services community values every submitted
issue, but w
idelpivnitskiy opened a new issue, #3692:
URL: https://github.com/apache/logging-log4j2/issues/3692
log4j-bom is used to manage versions of different `log4j-*` artifacts.
However, if you look at how "Managed Dependencies" section is parsed by Maven
for the latest
[log4j-bom:2.24.3](https:/
github-actions[bot] merged PR #188:
URL: https://github.com/apache/logging-log4j-tools/pull/188
--
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: notifica
jhl221123 opened a new pull request, #3691:
URL: https://github.com/apache/logging-log4j2/pull/3691
This PR addresses issue #3176 by ensuring scripts defined in the global
`` container have explicit, non-blank names. It also introduces a
clearer distinction between user-defined names and in
github-actions[bot] commented on PR #3691:
URL: https://github.com/apache/logging-log4j2/pull/3691#issuecomment-2910445243
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
