notifications  

Messages by Thread

• • Re: [I] Create dependency injection metadata index [logging-log4j2] via GitHub
  • Re: [I] Create dependency injection metadata index [logging-log4j2] via GitHub
  • Re: [I] Create dependency injection metadata index [logging-log4j2] via GitHub
  • Re: [I] Create dependency injection metadata index [logging-log4j2] via GitHub
• [PR] Fix: Ensure jvmrunargs lookup is always registered (fixes #2726) [logging-log4j2] via GitHub
  • Re: [PR] Fix: Ensure jvmrunargs lookup is always registered (fixes #2726) [logging-log4j2] via GitHub
  • Re: [PR] Fix: Ensure jvmrunargs lookup is always registered (fixes #2726) [logging-log4j2] via GitHub
  • Re: [PR] Fix: Ensure jvmrunargs lookup is always registered (fixes #2726) [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
  • Re: [PR] Remove `jvmrunargs` lookup [logging-log4j2] via GitHub
• Re: [I] Uniformize TLS configuration [logging-log4j2] via GitHub
  • Re: [I] Uniformize TLS configuration [logging-log4j2] via GitHub
  • Re: [I] Uniformize TLS configuration [logging-log4j2] via GitHub
• Re: [PR] Bump org.assertj:assertj-core from 3.27.3 to 3.27.4 [logging-log4j-transform] via GitHub
• [I] Add support for old-style exception rendering in Pattern Layout [logging-log4j2] via GitHub
  • Re: [I] Add support for old-style exception rendering in Pattern Layout [logging-log4j2] via GitHub
  • Re: [I] Add support for old-style exception rendering in Pattern Layout [logging-log4j2] via GitHub
  • Re: [I] Add support for old-style exception rendering in Pattern Layout [logging-log4j2] via GitHub
  • Re: [I] Add support for old-style exception rendering in Pattern Layout [logging-log4j2] via GitHub
• [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
  • Re: [PR] Add trailing newlines and emit formatted JSON [logging-log4j-transform] via GitHub
• [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round initialTime in RollingFileManager [logging-log4j2] via GitHub
  • Re: [PR] Round `initialTime` in `RollingFileManager` [logging-log4j2] via GitHub
• [I] Log4j2 metadata issues when ThresholdFilter is being used with GraalVM [logging-log4j2] via GitHub
  • Re: [I] Log4j2 metadata issues when ThresholdFilter is being used with GraalVM [logging-log4j2] via GitHub
  • Re: [I] Log4j2 metadata issues when ThresholdFilter is being used with GraalVM [logging-log4j2] via GitHub
• Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
  • Re: [I] The `jvmrunargs` lookup is always empty [logging-log4j2] via GitHub
• [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
  • Re: [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
  • Re: [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
  • Re: [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
  • Re: [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
  • Re: [I] Replace `@NameProvider` and `@AliasesProvider` registration of strategies in `ConfigurableInstanceFactory` [logging-log4j2] via GitHub
• Re: [PR] Bump commons-cli:commons-cli from 1.9.0 to 1.10.0 [logging-log4j-transform] via GitHub
• [I] Consolidate and Rename Log4j Converter Modules [logging-log4j-transform] via GitHub
• [I] `appenderRefs` in v1 properties files not handled correctly [logging-log4j-transform] via GitHub
  • Re: [I] `appenderRefs` in v1 properties files not handled correctly [logging-log4j-transform] via GitHub
  • Re: [I] `appenderRefs` in v1 properties files not handled correctly [logging-log4j-transform] via GitHub
  • Re: [I] `appenderRefs` in v1 properties files not handled correctly [logging-log4j-transform] via GitHub
  • Re: [I] `appenderRefs` in v1 properties files not handled correctly [logging-log4j-transform] via GitHub
• [I] Transformation to `v2:json` does not produce a pretty-printed file [logging-log4j-transform] via GitHub
  • Re: [I] Transformation to `v2:json` does not produce a pretty-printed file [logging-log4j-transform] via GitHub
  • Re: [I] Transformation to `v2:json` does not produce a pretty-printed file [logging-log4j-transform] via GitHub
  • Re: [I] Transformation to `v2:json` does not produce a pretty-printed file [logging-log4j-transform] via GitHub
  • Re: [I] Transformation to `v2:json` does not produce a pretty-printed file [logging-log4j-transform] via GitHub
• Re: [I] Possibility to inject custom ThreadContextStack implementation [logging-log4j2] via GitHub
  • Re: [I] Possibility to inject custom ThreadContextStack implementation [logging-log4j2] via GitHub
  • Re: [I] Possibility to inject custom ThreadContextStack implementation [logging-log4j2] via GitHub
• [PR] Avoid occasional failures in SocketAppenderTestCase on MacOS [logging-log4cxx] via GitHub
  • Re: [PR] Avoid occasional failures in SocketAppenderTestCase on MacOS [logging-log4cxx] via GitHub
• [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
  • Re: [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
  • Re: [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
  • Re: [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
  • Re: [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
  • Re: [PR] Use doxygen 1.14 to get a more modern looking web site [logging-log4cxx] via GitHub
• [PR] Synchronize Log4jLogEvent-related changes from 2.x [logging-log4j2] via GitHub
  • Re: [PR] Synchronize Log4jLogEvent-related changes from 2.x [logging-log4j2] via GitHub
  • Re: [PR] Synchronize Log4jLogEvent-related changes from 2.x [logging-log4j2] via GitHub
  • Re: [PR] Synchronize Log4jLogEvent-related changes from 2.x [logging-log4j2] via GitHub
  • Re: [PR] Synchronize Log4jLogEvent-related changes from 2.x [logging-log4j2] via GitHub
• [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
  • Re: [PR] Fix sizing of Maps [logging-log4j2] via GitHub
• [PR] Adjust GcpLayout JSON to latest format (#3586) [logging-log4j2] via GitHub
  • Re: [PR] Adjust GcpLayout JSON to latest format (#3586) [logging-log4j2] via GitHub
• [PR] Fix formatting of `s` pattern (#3469) [logging-log4j2] via GitHub
  • Re: [PR] Fix formatting of `s` pattern (#3469) [logging-log4j2] via GitHub
• [PR] Improve configuration error handling of HttpAppender (#3438) [logging-log4j2] via GitHub
  • Re: [PR] Improve configuration error handling of HttpAppender (#3438) [logging-log4j2] via GitHub
• [PR] Put 1.5.0 release date onto web site [logging-log4cxx] via GitHub
  • Re: [PR] Put 1.5.0 release date onto web site [logging-log4cxx] via GitHub
• [PR] Support `AsyncAppender::requiresLocation` [logging-log4j2] via GitHub
  • Re: [PR] Support `AsyncAppender::requiresLocation` [logging-log4j2] via GitHub
• Re: [PR] Bump log4j-api.version from 2.24.3 to 2.25.1 [logging-log4j2] via GitHub
  • Re: [PR] Bump log4j-api.version from 2.24.3 to 2.25.1 [logging-log4j2] via GitHub
• [PR] Support `FailoverAppender::requiresLocation` [logging-log4j2] via GitHub
  • Re: [PR] Support `FailoverAppender::requiresLocation` [logging-log4j2] via GitHub
  • Re: [PR] Support `FailoverAppender::requiresLocation` [logging-log4j2] via GitHub
  • Re: [PR] Support `FailoverAppender::requiresLocation` [logging-log4j2] via GitHub
  • Re: [PR] Support `FailoverAppender::requiresLocation` [logging-log4j2] via GitHub
• [PR] Use garbage-free formatter for `s` and `S` patterns (#3338) [logging-log4j2] via GitHub
  • Re: [PR] Use garbage-free formatter for `s` and `S` patterns (#3338) [logging-log4j2] via GitHub
• [PR] Reopen log file when rollover is unsuccessful (#3226) [logging-log4j2] via GitHub
  • Re: [PR] Reopen log file when rollover is unsuccessful (#3226) [logging-log4j2] via GitHub
  • Re: [PR] Reopen log file when rollover is unsuccessful (#3226) [logging-log4j2] via GitHub
  • Re: [PR] Reopen log file when rollover is unsuccessful (#3226) [logging-log4j2] via GitHub
  • Re: [PR] Reopen log file when rollover is unsuccessful (#3226) [logging-log4j2] via GitHub
• [PR] Document API compatibility checks (#3175) [logging-log4j2] via GitHub
  • Re: [PR] Document API compatibility checks (#3175) [logging-log4j2] via GitHub
• Re: [I] Replace withers with setters in `main` [logging-log4j2] via GitHub
• Re: [I] Core tests should migrate from XML to JSON [logging-log4j2] via GitHub
  • Re: [I] Core tests should migrate from XML to JSON [logging-log4j2] via GitHub
• [PR] feat(blog): Add post on VEX files and the new VEX Initiative [logging-site] via GitHub
  • Re: [PR] feat(blog): Add post on VEX files and the new VEX Initiative [logging-site] via GitHub
• [I] You can't ask everybody to upgrade to 2.15 at once. And the `formatMsgNoLookups` option is available to log4j ≥ 2.10 only. [logging-log4j2] via GitHub
  • Re: [I] No [logging-log4j2] via GitHub
• Re: [PR] Bump com.android.application from 8.11.0 to 8.11.1 in the all group across 1 directory [logging-log4j-samples] via GitHub
• Re: [PR] Bump graalvm/setup-graalvm from 1.3.4 to 1.3.5 in the all group [logging-log4j-samples] via GitHub
• [PR] Escape any logger name '&' or '"' in html attribute data [logging-log4cxx] via GitHub
  • Re: [PR] Escape any thread name '&' or '"' in html attribute data [logging-log4cxx] via GitHub
• [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
  • Re: [PR] Add org.apache.logging.log4j.core.appender.FileManager.getPath() [logging-log4j2] via GitHub
• Re: [PR] Bump org.apache.commons:commons-lang3 from 3.17.0 to 3.18.0 in /log4j-parent [logging-log4j2] via GitHub
• [PR] Specify the scale (seconds) of the monitorInterval configuration integer [logging-log4j2] via GitHub
  • Re: [PR] Specify the scale (seconds) of the monitorInterval configuration integer [logging-log4j2] via GitHub
• [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
  • Re: [PR] ConsoleAppender: Fix missing default Target value [logging-log4j2] via GitHub
• [PR] DefaultLayout: Append a newline to the serialized LogEvent [logging-log4j2] via GitHub
  • Re: [PR] DefaultLayout: Append a newline to the serialized LogEvent [logging-log4j2] via GitHub
  • Re: [PR] DefaultLayout: Append a newline to the serialized LogEvent [logging-log4j2] via GitHub
• Re: [PR] Bump commons-io:commons-io from 2.19.0 to 2.20.0 [logging-log4j-transform] via GitHub
• [I] log4j-iostreams in 3.0.0-beta2 has bug [logging-log4j2] via GitHub
  • Re: [I] log4j-iostreams in 3.0.0-beta2 has bug that fails logCaptor [logging-log4j2] via GitHub
  • Re: [I] log4j-iostreams in 3.0.0-beta2 has bug that fails logCaptor [logging-log4j2] via GitHub

• Earlier messages
• Later messages