gmane.comp.jakarta.log4j.devel archive
384 archived articles, newest first (page 2 of 4). Latest articles →
Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2]
Thu, 18 Jun 2026 08:01:49 -0000Re: [D] log4j 2 throws log4j 1 warnings [logging-log4j2]
Thu, 18 Jun 2026 06:25:43 -0000Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2]
Tue, 16 Jun 2026 18:35:36 -0000Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2]
Mon, 15 Jun 2026 16:45:07 -0000Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2]
Mon, 15 Jun 2026 16:43:36 -0000[D] No use of `inline` in `log4j-api-kotlin`? [log ging-log4j2]
Mon, 15 Jun 2026 10:19:37 -0000[ANN] Pax Web 11.1.2, Pax Web 10.1.0 and Pax Web 8.0.36 released
Thu, 11 Jun 2026 11:06:33 +0200Re: [D] Next Log4cxx Major release thoughts [logging-log4c xx]
Sun, 07 Jun 2026 05:16:46 -0000Re: [D] Next Log4cxx Major release thoughts [logging-log4c xx]
Sun, 07 Jun 2026 05:14:38 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Thu, 04 Jun 2026 18:55:05 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Thu, 04 Jun 2026 15:49:30 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Thu, 04 Jun 2026 15:44:17 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 19:54:12 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 18:12:09 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 17:06:03 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 14:13:35 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 14:11:56 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Wed, 03 Jun 2026 14:10:22 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 20:33:32 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 20:20:01 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 19:55:10 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 19:53:05 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 19:48:58 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 19:42:17 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Tue, 02 Jun 2026 19:25:25 -0000Re: [D] Removing `StructuredDataMessage` and all other R FC 5424 et al. [logging-log4j2]
Tue, 02 Jun 2026 19:03:24 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Tue, 02 Jun 2026 18:08:33 -0000[D] Removing `StructuredDataMessage` and all other RFC 542 4 et al. [logging-log4j2]
Tue, 02 Jun 2026 17:52:05 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Tue, 02 Jun 2026 14:26:41 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Tue, 02 Jun 2026 14:15:29 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Tue, 02 Jun 2026 13:43:16 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Mon, 01 Jun 2026 17:13:15 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Mon, 01 Jun 2026 14:08:34 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Mon, 01 Jun 2026 13:02:14 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Sun, 31 May 2026 21:04:13 -0000Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Sun, 31 May 2026 21:03:21 -0000[ANNOUNCE] WicketStuff 9.23.1 Released
Sun, 31 May 2026 07:27:47 +0700Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content) ? [logging-log4j2]
Sat, 30 May 2026 15:53:59 -0000[D] Threat model: how should Thread Context (MDC) keys b e classified (trusted structural or untrusted content)? [ logging-log4j2]
Sat, 30 May 2026 13:06:31 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Thu, 21 May 2026 11:55:47 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Thu, 21 May 2026 11:12:45 -0000JDK 27 Approaches Rampdown | Final Field Mutation Warnings Heads-up
Thu, 21 May 2026 08:01:30 +0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Thu, 21 May 2026 05:56:00 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Thu, 21 May 2026 05:32:22 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Wed, 20 May 2026 11:50:22 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Wed, 20 May 2026 10:57:00 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Wed, 20 May 2026 10:03:34 -0000Re: [D] Poll: Dropping net462 Support in log4net [loggin g-log4net]
Wed, 20 May 2026 09:15:00 -0000Re: Archiving inactive project repositories
Mon, 18 May 2026 12:39:47 -0700Re: Archiving inactive project repositories
Mon, 18 May 2026 21:14:50 +0200Archiving inactive project repositories
Mon, 18 May 2026 10:47:03 +0200[PR] [INFRA] Set up default rulesets for default and relea se branches [logging-log4j-flume]
Fri, 15 May 2026 22:14:59 -0000The scheme https s not consistent with the TLS enabled setting (Re: [ANN] Apache Tomcat 11.0.22 Available)
Tue, 12 May 2026 10:36:12 +0200Introduction: Ramanathan (ramanathan)
Sun, 10 May 2026 22:10:35 +0530Re: New committer: Ramanathan Muthu
Sun, 10 May 2026 19:01:52 +0530New committer: Ramanathan Muthu
Sun, 10 May 2026 14:08:36 +0200Re: [ANNOUNCE] Apache Wicket 10.9.0 released
Fri, 8 May 2026 06:43:58 -0400[ANNOUNCE] Apache Log4j `2.26.0` released
Thu, 7 May 2026 10:59:55 +0200[RESULT][VOTE] Release Apache Log4j `2.26.0`
Thu, 7 May 2026 10:12:34 +0200Re: MoreLikeThis Query Parser request across multiple SolrCloud collections fails
Wed, 6 May 2026 20:49:56 +0300Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 19:39:12 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 17:38:31 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 23:35:26 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 17:30:39 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 23:10:13 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 07:26:16 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Tue, 5 May 2026 07:14:37 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 22:49:38 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 21:08:47 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 15:01:25 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 14:57:48 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 14:55:55 -0400Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 20:49:42 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 20:18:55 +0200Re: [VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 08:16:51 -0400Re: [D] Potential ETA on a Log4j 2.26.0 release [loggi ng-log4j2]
Mon, 04 May 2026 10:21:49 -0000Re: [D] Potential ETA on a Log4j 2.26.0 release [loggi ng-log4j2]
Mon, 04 May 2026 10:21:08 -0000Re: [D] Potential ETA on a Log4j 2.26.0 release [loggi ng-log4j2]
Mon, 04 May 2026 09:23:14 -0000[VOTE] Release Apache Log4j `2.26.0`
Mon, 4 May 2026 09:45:47 +0200Re: [D] Timeline for org.apache.logging.log4j:log4j- api:3.0.0 release? [logging-log4j2]
Sat, 02 May 2026 15:47:40 -0000Re: [log4j] CI is broken, a decision needs to be made
Fri, 1 May 2026 09:15:03 +0200Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 17:33:11 -0500Apache MINA 2.0.12 and 2.2.7 release
Thu, 30 Apr 2026 23:52:01 +0200Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 12:55:30 -0700Re: [RESULT][VOTE] Release Apache Fluss 0.9.1-incubating-rc1
Thu, 30 Apr 2026 21:05:25 +0300Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 19:48:15 +0200Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 09:48:25 -0700Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 18:40:14 +0200Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 09:39:26 -0700Re: [log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 09:17:31 -0400[log4j] CI is broken, a decision needs to be made
Thu, 30 Apr 2026 15:09:53 +0200Re: [log4j] Ramp down for `2.26.0`
Tue, 28 Apr 2026 17:57:29 -0400Re: [log4j] Ramp down for `2.26.0`
Tue, 28 Apr 2026 23:52:41 +0200Re: [log4j] Ramp down for `2.26.0`
Tue, 28 Apr 2026 17:48:38 -0400Re: [log4j] Ramp down for `2.26.0`
Tue, 28 Apr 2026 23:44:44 +0200Re: [D] Deprecate the Log4j Scala API [logging-log4j2]
Tue, 28 Apr 2026 02:38:39 -0000Re: [D] Deprecate the Log4j Scala API [logging-log4j2]
Tue, 28 Apr 2026 02:38:05 -0000Re: [D] Deprecate the Log4j Scala API [logging-log4j2]
Tue, 28 Apr 2026 02:36:42 -0000Re: [D] Deprecate the Log4j Scala API [logging-log4j2]
Tue, 28 Apr 2026 02:36:32 -0000Re: [D] Deprecate the Log4j Scala API [logging-log4j2]
Tue, 28 Apr 2026 02:38:21 -0000
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.