swebb2066 opened a new pull request, #323:
URL: https://github.com/apache/logging-log4cxx/pull/323
The generated documentation also excludes ABI changes.
--
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
swebb2066 opened a new pull request, #322:
URL: https://github.com/apache/logging-log4cxx/pull/322
(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
swebb2066 merged PR #321:
URL: https://github.com/apache/logging-log4cxx/pull/321
--
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
jvz commented on issue #2117:
URL:
https://github.com/apache/logging-log4j2/issues/2117#issuecomment-1869806619
I like this idea because it also supports use of other file system
implementations based on what the user has installed. That could also be useful
in tests if we used something l
jvz commented on issue #2100:
URL:
https://github.com/apache/logging-log4j2/issues/2100#issuecomment-1869806222
Yes, I covered that point in
> Advanced methods of handling configuration (such as a refresh period for
the config file, JMX remote management, or other remote methods for
jvz commented on issue #2116:
URL:
https://github.com/apache/logging-log4j2/issues/2116#issuecomment-1869804088
So I'm going to note that we're [removing the system properties for
specifying classes](https://github.com/apache/logging-log4j2/issues/1977); you
can currently register your own
jvz commented on issue #59:
URL:
https://github.com/apache/logging-log4j-kotlin/issues/59#issuecomment-1869796794
Yes, I like this idea. Once that is in place, we can even implement some
minimal multi-platform implementations (e.g., there's a common `println` and
`readln` function for all
jvz commented on issue #2111:
URL:
https://github.com/apache/logging-log4j2/issues/2111#issuecomment-1869795665
This is a long-known issue specific to macOS because by default, macOS does
not include an entry in `/etc/hosts` for `localhost`, so the default behavior
of its network stack (or
jvz commented on issue #2025:
URL:
https://github.com/apache/logging-log4j2/issues/2025#issuecomment-1869794722
@ppkarwasz sounds like a good idea to me!
--
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 t
centic9 commented on issue #2129:
URL:
https://github.com/apache/logging-log4j2/issues/2129#issuecomment-1869751522
In order to provide a minimal reproducer I have prepared a branch at
https://github.com/centic9/poi-on-android/tree/log4j_2_22_0_minimal_reproducer
which is a minimal Android
centic9 opened a new issue, #2129:
URL: https://github.com/apache/logging-log4j2/issues/2129
## Description
When upgrading an Android Application which has a transitive dependency on
Log4j from log4j-core 2.21.1 to 2.22.0, it fails with an exception because it
seems the method Access
ppkarwasz commented on issue #2023:
URL:
https://github.com/apache/logging-log4j2/issues/2023#issuecomment-1869666818
Issue #2117 is related to this.
--
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
ppkarwasz commented on issue #2023:
URL:
https://github.com/apache/logging-log4j2/issues/2023#issuecomment-1869496088
@tcmot,
Thanks for the suggestion. Your solution will cause two system calls (a
[`write`](https://man7.org/linux/man-pages/man2/write.2.html) and an
[`fsync/fdatasyn
ppkarwasz commented on issue #2025:
URL:
https://github.com/apache/logging-log4j2/issues/2025#issuecomment-1869492980
@jvz,
I investigated the effects of `flush()` on the `FileAppender` a little bit
further and it is a no-op in `FileOutputStream` (the output stream does not use
any
14 matches
Mail list logo
