swebb2066 opened a new pull request, #441:
URL: https://github.com/apache/logging-log4cxx/pull/441
1. Allow MultiprocessRollingFileAppender in a configuration when log4cxx is
statically linked (Fixes #440)
2. Resolve error "Can't cast writer to FileOutputStream" (Fixes #439)
--
Thi
swebb2066 merged PR #438:
URL: https://github.com/apache/logging-log4cxx/pull/438
--
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-unsubscr
vy commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876731842
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.log4j.mes
ppkarwasz commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876726904
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.lo
vy commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876721234
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.log4j.mes
ppkarwasz commented on issue #3282:
URL:
https://github.com/apache/logging-log4j2/issues/3282#issuecomment-2529335265
> shall we document this unexpected behavior of `%xEx` and
[JDK-8037342](https://bugs.openjdk.org/browse/JDK-8037342) encourage users to
prefer `%ex` instead?
Sure,
ppkarwasz commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876674213
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.lo
ppkarwasz commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876674213
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.lo
vy commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876611981
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.log4j.mes
ppkarwasz commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876619424
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.lo
ppkarwasz commented on PR #151:
URL:
https://github.com/apache/logging-log4j-transform/pull/151#issuecomment-2529177060
> (AFAIU, this has never been released with `log4j-transform` – please
correct me if I'm wrong.)
No, it has never been released, so the appropriate time to remove i
ppkarwasz commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876576932
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.lo
vy commented on issue #3282:
URL:
https://github.com/apache/logging-log4j2/issues/3282#issuecomment-2529194672
@ppkarwasz, shall we document this unexpected behavior of `%xEx` and
[JDK-8037342](https://bugs.openjdk.org/browse/JDK-8037342) encourage users to
prefer `%ex` instead?
--
This
vy commented on code in PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263#discussion_r1876557002
##
log4j-core-test/src/test/java/org/apache/logging/log4j/core/LoggerMessageFactoryCustomizationTest.java:
##
@@ -24,34 +24,36 @@
import org.apache.logging.log4j.mes
kelunik commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2528936360
Thanks for providing these details!
--
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
jpcmonster commented on issue #3252:
URL:
https://github.com/apache/logging-log4j2/issues/3252#issuecomment-2528061876
@ppkarwasz yes, I think I can try that fairly easily for you this morning;
will circle back as soon as I know.
--
This is an automated message from the Apache Git Servic
ppkarwasz commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2527989952
> > @garydgregory, I would wait a couple of weeks to see if other bugs are
reported, but, yes, I think we should release a 2.24.3.
>
> Why? Can't you just release 2.24.4 if
garydgregory commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2527973880
@kelunik
Because it takes time and effort for the release manager to create a release
candidate and it takes time for PMC members to review that candidate. It's not
free e
kelunik commented on issue #3234:
URL:
https://github.com/apache/logging-log4j2/issues/3234#issuecomment-2527893775
Thank you @ppkarwasz, was just about to report this! 🙈
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
kelunik commented on PR #3235:
URL: https://github.com/apache/logging-log4j2/pull/3235#issuecomment-2527886103
> @garydgregory, I would wait a couple of weeks to see if other bugs are
reported, but, yes, I think we should release a 2.24.3.
Why? Can't you just release 2.24.4 if another
ppkarwasz commented on PR #3071:
URL: https://github.com/apache/logging-log4j2/pull/3071#issuecomment-2527849216
@ahasbini,
Please open a [GitHub
Discussion](https://github.com/apache/logging-log4j2/discussions) or ask on
[the `log4j-user@logging` mailing
list](https://logging.apach
ahasbini commented on PR #3071:
URL: https://github.com/apache/logging-log4j2/pull/3071#issuecomment-2527834329
When will this merge be released?
--
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 t
ppkarwasz commented on issue #3252:
URL:
https://github.com/apache/logging-log4j2/issues/3252#issuecomment-2527370096
@jpcmonster,
Can you check if our `2.24.3-SNAPSHOT` snapshot fixes your problem? See
[downloads](https://logging.apache.org/download.html) for the URL of our
snapsho
BigMichi1 opened a new issue, #440:
URL: https://github.com/apache/logging-log4cxx/issues/440
when building log4cxx as a static lib the `MultiprocessRollingFileAppender`
is not available when used in the configuration XML.
when adding this line somewhere in the code
```cpp
a
ppkarwasz closed issue #3283: ConcurrectModificationException while adjusting
log-level in runtime
URL: https://github.com/apache/logging-log4j2/issues/3283
--
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
ppkarwasz commented on issue #3283:
URL:
https://github.com/apache/logging-log4j2/issues/3283#issuecomment-2527229864
Closing as duplicate of #3234.
--
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
BigMichi1 opened a new issue, #439:
URL: https://github.com/apache/logging-log4cxx/issues/439
when adding a `MultiprocessRollingFileAppender` to `log4cxx.xml` like in the
following snippet
```xml
http://jakarta.apache.org/log4j/";>
ppkarwasz merged PR #3263:
URL: https://github.com/apache/logging-log4j2/pull/3263
--
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
28 matches
Mail list logo
