github-actions[bot] commented on PR #3217:
URL: https://github.com/apache/logging-log4j2/pull/3217#issuecomment-2493089453
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ppkarwasz commented on PR #3226:
URL: https://github.com/apache/logging-log4j2/pull/3226#issuecomment-2493081887
@king-tyler,
Thank You for your contribution! :100:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
ppkarwasz merged PR #3226:
URL: https://github.com/apache/logging-log4j2/pull/3226
--
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-unsubsc
ppkarwasz commented on code in PR #3195:
URL: https://github.com/apache/logging-log4j2/pull/3195#discussion_r1853398829
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/config/plugins/processor/PluginProcessorPublicSetterTest.java:
##
@@ -0,0 +1,107 @@
+/*
+ * Lice
ppkarwasz closed issue #2592: After a log file is deleted by mistake, a new
rollover file cannot be created.
URL: https://github.com/apache/logging-log4j2/issues/2592
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
github-actions[bot] merged PR #159:
URL: https://github.com/apache/logging-log4j-tools/pull/159
--
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
ppkarwasz commented on issue #3196:
URL:
https://github.com/apache/logging-log4j2/issues/3196#issuecomment-2492956007
@xzel23,
We generate the date in the release notes using [our internal
`log4j-changelog-maven-plugin`](https://logging.apache.org/log4j/tools/log4j-changelog-maven-pl
jaykataria commented on issue #2079:
URL:
https://github.com/apache/logging-log4j2/issues/2079#issuecomment-2492889240
Hi @ppkarwasz , is this issue still open, can you provide, some detail on
this, maybe I can pick it up 😄
--
This is an automated message from the Apache Git Service
king-tyler closed pull request #3021: Fix FileRenameAction when the source file
doesn't exist
URL: https://github.com/apache/logging-log4j2/pull/3021
--
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
king-tyler commented on PR #3021:
URL: https://github.com/apache/logging-log4j2/pull/3021#issuecomment-2492845407
> @king-tyler,
>
> Do you plan some changes in this PR or should I close it in favor of #3226?
This one can be closed
--
This is an automated message from the Apa
swebb2066 opened a new pull request, #432:
URL: https://github.com/apache/logging-log4cxx/pull/432
(no comment)
--
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 unsubscri
github-actions[bot] merged PR #67:
URL: https://github.com/apache/logging-log4j-scala/pull/67
--
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: notificati
ppkarwasz closed issue #3196: log4j-api 2.24.1 causes getLogger() to return
null when using log4j-core 2.24.0
URL: https://github.com/apache/logging-log4j2/issues/3196
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
ppkarwasz commented on issue #3196:
URL:
https://github.com/apache/logging-log4j2/issues/3196#issuecomment-2492527100
@ed-erwin-tf,
Please, use our [`log4j-bom`
BOM](https://logging.apache.org/log4j/2.x/components.html) to manage
dependencies, see our [Installation guide for more
d
ppkarwasz commented on issue #3196:
URL:
https://github.com/apache/logging-log4j2/issues/3196#issuecomment-2492522205
Closing this, since [release
`2.24.2`](https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.24.2)
fixes the NPE.
--
This is an automated message from the Apache
ppkarwasz closed issue #3169: ExceptionInitailizationError in log4j JUL
URL: https://github.com/apache/logging-log4j2/issues/3169
--
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.
ppkarwasz commented on issue #3169:
URL:
https://github.com/apache/logging-log4j2/issues/3169#issuecomment-2492521257
Closing this, since [release
`2.24.2`](https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.24.2)
should fix it.
--
This is an automated message from the Apache
ed-erwin-tf commented on issue #3196:
URL:
https://github.com/apache/logging-log4j2/issues/3196#issuecomment-2492241906
I was running into this problem with using poi. I was declaring a specific
version of log4j-core (2.24.0 or 2.24.1), not realizing that poi was declaring
an older versio
github-actions[bot] commented on PR #3226:
URL: https://github.com/apache/logging-log4j2/pull/3226#issuecomment-2491528068
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ppkarwasz commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2491011731
@kangarko,
I am not a Nashorn committer, sorry.
PaperMC **does** use `log4j-jul`: see the [`libs.version.toml`
file](https://github.com/PaperMC/Velocity/blob/dev/3.0
king-tyler commented on code in PR #3226:
URL: https://github.com/apache/logging-log4j2/pull/3226#discussion_r1852295422
##
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/RollingFileManager.java:
##
@@ -506,9 +506,16 @@ public synchronized void rollover(
ppkarwasz merged PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125
--
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-unsubsc
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2491040252
@ppkarwasz Thank you, you made my day with this fix!!!
I will add a note to our customers so that they can adjust their server
system properties for now.
--
This is an a
ppkarwasz commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2491026245
@kangarko,
The workaround for this bug was provided by the reporter in [this
comment](https://github.com/apache/logging-log4j2/issues/3119#issuecomment-2437209081):
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2491021035
Gotcha, thanks for the that, I have passed them the relevant information. I
am unfortunately not a Paper maintainer eithe.r
--
This is an automated message from the Apache Git S
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2490891232
@ppkarwasz I tried loading the snapshot before nashorn, but I am still
getting the error. If you know of any solutions I'd greatly appreciate it!
**Stack trace:**
htt
github-actions[bot] commented on PR #3227:
URL: https://github.com/apache/logging-log4j2/pull/3227#issuecomment-2490953363
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ppkarwasz closed issue #3119: log4j-jul adapter makes code throws NPEs
URL: https://github.com/apache/logging-log4j2/issues/3119
--
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.
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2490938151
@ppkarwasz could you please provide nashorn-core snapshot, instead? Because
production is affected since October, I could just use the snapshot for now.
Many thanks.
--
This is
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2490897478
Or the easiest way would be just to download the nashorn-core snapshot, is
there a repo, please?
--
This is an automated message from the Apache Git Service.
To respond to the m
kangarko commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2490846779
@ppkarwasz appreciated it, unfortunately we rely on the Velocity software
which uses said library, I found out the problem started since of this commit:
https://github.com/PaperMC
github-actions[bot] merged PR #288:
URL: https://github.com/apache/logging-parent/pull/288
--
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
AlbaHerrerias opened a new pull request, #3227:
URL: https://github.com/apache/logging-log4j2/pull/3227
Hello 👋
We are from Neighbourhoodie, the implementation partner of the STF Bug
Resilience Program. This work is part of our agreed Milestone 1. Upgrade from
JUnit 4 to JUnit 5. Thi
ppkarwasz commented on PR #3125:
URL: https://github.com/apache/logging-log4j2/pull/3125#issuecomment-2490779679
@kangarko,
Can you check if the latest `2.25.0-SNAPSHOT` solves your problem with
Nashorn? The URL of our Maven snapshot repository is on [our download
page](https://loggi
ppkarwasz commented on PR #3021:
URL: https://github.com/apache/logging-log4j2/pull/3021#issuecomment-2490634890
@king-tyler,
Do you plan some changes in this PR or should I close it in favor of #3226?
--
This is an automated message from the Apache Git Service.
To respond to the me
ppkarwasz commented on code in PR #3226:
URL: https://github.com/apache/logging-log4j2/pull/3226#discussion_r1851632621
##
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/RollingFileManager.java:
##
@@ -506,9 +506,16 @@ public synchronized void rollover()
36 matches
Mail list logo
