[I] RollingFileAppender opens up more basic methods for extension to improve scalabilityexten (logging-log4net)

2024-08-12 Thread via GitHub
RunWangusst opened a new issue, #167: URL: https://github.com/apache/logging-log4net/issues/167 I want to customize my roll files name, currently roll file names will rename to origin file name of with suffix .1 .2 .3 and so on. So my log files will like this: **log.txt.1** **log.txt.2**

Re: [PR] Bump com.google.errorprone:error_prone_core from 2.29.2 to 2.30.0 [logging-parent]

2024-08-12 Thread via GitHub
github-actions[bot] closed pull request #222: Bump com.google.errorprone:error_prone_core from 2.29.2 to 2.30.0 URL: https://github.com/apache/logging-parent/pull/222 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Re: [PR] Bump org.slf4j:slf4j-api from 1.7.36 to 2.0.16 (logging-log4j2)

2024-08-12 Thread via GitHub
github-actions[bot] closed pull request #2828: Bump org.slf4j:slf4j-api from 1.7.36 to 2.0.16 URL: https://github.com/apache/logging-log4j2/pull/2828 -- 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

Re: [I] RollingFileAppender opens up more basic methods for extension to improve scalabilityexten (logging-log4net)

2024-08-12 Thread via GitHub
FreeAndNil commented on issue #167: URL: https://github.com/apache/logging-log4net/issues/167#issuecomment-2283658381 Hi @RunWangusst, have you tried using PreserveLogFileNameExtension? ``` ... ``` -- This is an automated message from th

Re: [PR] Port appenders documentation to `main` (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz merged PR #2805: URL: https://github.com/apache/logging-log4j2/pull/2805 -- 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

Re: [I] [MS13] Automate website deployment (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz closed issue #2476: [MS13] Automate website deployment URL: https://github.com/apache/logging-log4j2/issues/2476 -- 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 un

[I] [MS21] Native Compilation Support #1 (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz opened a new issue, #2830: URL: https://github.com/apache/logging-log4j2/issues/2830 This is the first milestone devoted to fixing GraalVM support in Log4j. ## Tasks - [x] Fix GraalVM support in `log4j-api` (#2392), - [ ] Release Log4j API 2.24.0 - [ ] Create and

Re: [I] [MS21] Native Compilation Support #1 (logging-log4j2)

2024-08-12 Thread via GitHub
vy commented on issue #2830: URL: https://github.com/apache/logging-log4j2/issues/2830#issuecomment-2283833828 @ppkarwasz, I'd really appreciate a dedicated `manual/native.adoc` such that: * It is linked from a bridging section in `installation.adoc` (at the bottom?) * It is neste

Re: [I] Configuration System Initialization Failure with PublishTrimmed in .NET 8 (logging-log4net)

2024-08-12 Thread via GitHub
tmoonlight commented on issue #165: URL: https://github.com/apache/logging-log4net/issues/165#issuecomment-2283874666 I have followed your method, but the issue with the PublishTrimmed program still persists. ![image](https://github.com/user-attachments/assets/1873fb7e-93c1-4009-847f-3a

Re: [I] Configuration System Initialization Failure with PublishTrimmed in .NET 8 (logging-log4net)

2024-08-12 Thread via GitHub
tmoonlight commented on issue #165: URL: https://github.com/apache/logging-log4net/issues/165#issuecomment-2283971381 Hi, The issue seems to be more complex than initially thought. I found that not only is log4net affected, but other parts of the code also encounter problems when trimmi

Re: [I] Configuration System Initialization Failure with PublishTrimmed in .NET 8 (logging-log4net)

2024-08-12 Thread via GitHub
FreeAndNil closed issue #165: Configuration System Initialization Failure with PublishTrimmed in .NET 8 URL: https://github.com/apache/logging-log4net/issues/165 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

Re: [I] Configuration System Initialization Failure with PublishTrimmed in .NET 8 (logging-log4net)

2024-08-12 Thread via GitHub
FreeAndNil commented on issue #165: URL: https://github.com/apache/logging-log4net/issues/165#issuecomment-2284049232 No problem - as you can see in #142 and #147 you are not the only one with those problems using aot. Feel free to reopen when you get new details. -- This is an automa

Re: [PR] opt-out of trimming until it works #142, #147, #165 (logging-log4net)

2024-08-12 Thread via GitHub
FreeAndNil commented on PR #166: URL: https://github.com/apache/logging-log4net/pull/166#issuecomment-2284050354 Closing as of now. -- 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 co

Re: [PR] opt-out of trimming until it works #142, #147, #165 (logging-log4net)

2024-08-12 Thread via GitHub
FreeAndNil closed pull request #166: opt-out of trimming until it works #142, #147, #165 URL: https://github.com/apache/logging-log4net/pull/166 -- 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 s

[I] [MS22] Native Compilation Support #2 (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz opened a new issue, #2831: URL: https://github.com/apache/logging-log4j2/issues/2831 This is the second milestone, after #2830, devoted to fixing GraalVM support in Log4j. ## Tasks - [ ] Fix GraalVM support in `log4j-core`. - [ ] Document how to use GraalVM with Lo

[I] [MS23] Native Compilation Support #3 (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz opened a new issue, #2832: URL: https://github.com/apache/logging-log4j2/issues/2832 This is the third milestone, after #2831, devoted to fixing GraalVM support in Log4j. ## Tasks - [ ] Fix GraalVM support in `log4j-json-template-layout`. -- This is an automate

[I] [MS24] Native Compilation Support #4 (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz opened a new issue, #2833: URL: https://github.com/apache/logging-log4j2/issues/2833 This is the final milestone, after #2832, devoted to fixing GraalVM support in Log4j. ## Tasks - [ ] Fix GraalVM support in all remaining Log4j modules. -- This is an automated

[PR] Add `ScopedContext` to version 2.25.0 (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz opened a new pull request, #2834: URL: https://github.com/apache/logging-log4j2/pull/2834 This PR reintroduces `ScopedContext` into version 2.25.0. We discussed about introducing a new `log4j-context` module, therefore it is not ready to be merged. -- This is an autom

Re: [PR] Bump org.slf4j:slf4j-api from 2.0.15 to 2.0.16 [logging-log4j-transform]

2024-08-12 Thread via GitHub
github-actions[bot] closed pull request #117: Bump org.slf4j:slf4j-api from 2.0.15 to 2.0.16 URL: https://github.com/apache/logging-log4j-transform/pull/117 -- 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

[I] Several ClassNotFoundException warnings after upgrading to 2.23.x (logging-log4j2)

2024-08-12 Thread via GitHub
mihalyr opened a new issue, #2835: URL: https://github.com/apache/logging-log4j2/issues/2835 ## Description Updating log4j from 2.22.1 to 2.23.0 or 2.23.1 causes a long list of warnings with exception traces for ClassNotFound exceptions for various class files. ## Configurati

Re: [I] Several ClassNotFoundException warnings after upgrading to 2.23.x (logging-log4j2)

2024-08-12 Thread via GitHub
ppkarwasz commented on issue #2835: URL: https://github.com/apache/logging-log4j2/issues/2835#issuecomment-2285449076 @mihalyr, The warning statements you are seeing were always present in the Log4j codebase, but were only visible if the `verbose` attribute of the configuration was