Re: [VOTE] Release Apache Log4j `2.25.2`

+1 I tested the source zip: - ASC OK - SHA512 OK - mvn clean verify Using: openjdk version "17.0.16" 2025-07-15 OpenJDK Runtime Environment Homebrew (build 17.0.16+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0.16+0, mixed mode, sharing) Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd

Re: [VERIFYING] Release Apache Log4net 3.2.0

On Wed, Aug 20, 2025 at 3:52 PM Jan Friedrich wrote: > > Hi Gary, > > Thanks for digging into this! Could you point out where the $ symbols > are missing in the release kit page? That’ll help us fix it quickly. I edited the page in GH with the edit button. It sounds like I am wrong in assuming t

Re: [RESULT][VOTE] Release Apache Log4cxx 1.5.0

Please listen the "..." Ty, Gary On Sun, Aug 3, 2025, 00:00 Stephen Webb wrote: > and here is my +1. > > With that the vote passed with 3 +1 votes from ... and myself. > I will continue the release process. > > Stephen > > > --

Re: [VOTE] Release Apache Log4cxx 1.5.0

Do I understand correctly that I need a local build of APR and APR-utils? Gary On Mon, Jul 28, 2025, 23:19 Stephen Webb wrote: > This is a vote to release the Apache Log4cxx 1.5.0. > > Website: https://logging.staged.apache.org/log4cxx/1.5.0/changelog.html > GitHub: https://github.com/apache/lo

Re: [DISCUSSION][VOTE] Release Apache Log4j `2.25.1` (RC1)

Dare I ask my our build has Gradle horror in it? Gary On Wed, Jul 9, 2025, 04:48 Piotr P. Karwasz wrote: > Hi Matt, > On 8.07.2025 22:14, Matt Sicker wrote: > > [image: gist-og-image-54fd7dc0713e.png] > > gist:54c8222bd8ef3dabd690994ab35d85d2 >

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

On Sat, Jul 5, 2025 at 5:54 PM Piotr P. Karwasz wrote: > > Hi Gary, > > On 5.07.2025 23:41, Gary Gregory wrote: > > But it failed with Docker tests enabled: mvn clean verify -Pdocker > > -D'docker.showLogs=true' > > > > [ERROR] DOCKER> [ela

Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)

+1 I tested the src zip file distribution: - GPG ok - SHA512 OK - mvn clean verify But it failed with Docker tests enabled: mvn clean verify -Pdocker -D'docker.showLogs=true' [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9

[ANNOUNCE] Apache Commons FileUpload 2.0.0-M4

://commons.apache.org/proper/commons-fileupload/ Download it from https://commons.apache.org/proper/commons-fileupload/download_fileupload.cgi Gary Gregory Apache Commons

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

eeping the Docker tests enabled elsewhere but I'm satisfied that the MongoDB tests passed in Docker by visual inspection. The ASC and SHA512 files are OK. Gary On Sat, Jun 14, 2025 at 12:16 PM Gary Gregory wrote: > > On Sat, Jun 14, 2025 at 11:27 AM Piotr P. Karwasz > wrote: &

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

On Sat, Jun 14, 2025 at 11:27 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On 14.06.2025 13:00, Gary Gregory wrote: > > On Sat, Jun 14, 2025 at 3:09 AM Piotr P. Karwasz > > wrote: > >> I hope this helps you debug what is going on during the ElasticSearch > >

Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.0` (RC1)

On Sat, Jun 14, 2025 at 3:09 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On 14.06.2025 03:22, Gary Gregory wrote: > > Running: > > > > mvn clean verify -Pdocker > > > > I.get: > > > > [INFO] DOCKER> Pulling from li

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

FWIW, I updated to: Docker version 28.2.2, build e6534b4 But the result is the same :( Gary On Fri, Jun 13, 2025 at 9:22 PM Gary Gregory wrote: > > Hi Piotr, > > Running: > > mvn clean verify -Pdocker > > I.get: > > [INFO] DOCKER> Pulling from library/e

Re: [VOTE] Release Apache Log4j `2.25.0` (RC1)

Hi Piotr, Running: mvn clean verify -Pdocker I.get: [INFO] DOCKER> Pulling from library/elasticsearch 4f4fb700ef54: Pull complete 917e7c84aa9f: Pull complete 9bc7cea61360: Pull complete 17932c3263b2: Pull complete e4eabb4d0724: Pull complete 89fc15b13be8: Pull complete e20dbb8c40e5: Pull comple

Re: Release 2.25.0

On Sun, May 25, 2025 at 11:18 AM Piotr P. Karwasz wrote: > > Hi all, > > On 16.05.2025 17:37, Piotr P. Karwasz wrote: > > I'm aiming to release Log4j 2.25.0 before the end of the month, with > > a release candidate planned for next weekend (May 24th). > > Just a quick update on the 2.25.0 release

Re: [VOTE] Release Apache Log4net 3.1.0

Ah, ty! Gary On Mon, May 12, 2025, 14:27 Jan Friedrich wrote: > See below: > > *@Gary: I will try to fix your issue outside of this release, because it > seems to be a special problem on you local machine.* > > Jan > > On 5/12/25 20:20, Gary Gregory wrote: > >

Re: [VOTE] Release Apache Log4net 3.1.0

What about the hanging build i reported? Gary On Mon, May 12, 2025, 14:11 Jan Friedrich wrote: > and here is my +1. > > With that the vote passed with 3 +1 votes from Volkan Yazıcı, Davyd > McColl and myself. > I will continue the release process. > > @Gary: I will try to fix your issue outside

Re: [VOTE] Release Apache Log4net 3.1.0

One day I'll learn how to read ALL the instructions 😉 Gary On Thu, May 8, 2025, 09:14 Jan Friedrich wrote: > See 2) Prerequisites (choco - *only in case of problems with winget*) > > Jan > > > On May 8, 2025 3:07:19 PM GMT+02:00, "Gary D. Gregory" < > ggreg...@apache.org> wrote: > >> Before I g

Re: [VOTE] Release Apache Log4net 3.1.0

lease.ps1` script. > > If I misunderstood your remark, would you mind elaborating it, please? > > On Thu, May 8, 2025 at 2:06 PM Gary Gregory > wrote: > > > Hi all, > > > > The review kit is not quite right IMO: One must at least review the > > source zip or tar

Re: [VOTE] Release Apache Log4net 3.1.0

Hi all, The review kit is not quite right IMO: One must at least review the source zip or tar ball. Reviewing a checkout of the sources is useful for devs but that's not what we deliver from my understanding of Apache rules; we deliver source files (not an svn repo). Would it be possible to add to

Re: Maven POM "Developers" section

Some IMOs below. On Fri, Mar 21, 2025 at 6:40 AM Piotr P. Karwasz wrote: > > Hi all, > > A user report regarding a broken link on `projects.apache.org`[1] > brought my attention to the amount of out-of-date metadata we publish: > > * Our DOAP file has not been updated in ages. It contained out of

Re: [VOTE] Add branch protection rules to Log4j

On Fri, Apr 4, 2025 at 4:07 AM Volkan Yazıcı wrote: > > On Wed, Apr 2, 2025 at 7:12 PM Piotr P. Karwasz > wrote: > > > Hi all, > > Sorry, my e-mail client reformatted some lines. > > So, the concerned repos are all non-dormant Java repos: l-admin, l-jdk, > > l-jmx-gui, l-log4j2, l-log4j-jakarta,

Re: Any updates on log4j 3.0.0 becoming GA?

Hi Piotr, Thank you for explaining your priorities for upcoming releases and setting expectations, this is very helpful 😀 Gary On Tue, Mar 25, 2025, 06:37 Piotr P. Karwasz wrote: > Hi Daniel, > > On 17.03.2025 15:19, Daniel Burrell wrote: > > Is a maintainer available to cut this 3.0.0 release

Re: Any updates on log4j 3.0.0 becoming GA?

Hello Daniel, We have 3.0.0-beta3 available for testing. It would be helpful if you could confirm your uses cases work with this version. Gary On Mon, Mar 17, 2025, 10:20 Daniel Burrell wrote: > Dear Apache Logging team, > > > Is a maintainer available to cut this 3.0.0 release? I believe a v

Re: Signaling configuration errors

I like the idea of a transactional configuration (all or nothing). Internally I think we should use a custom unchecked runtime exception which would be logged by us from our top level API. Gary On Mon, Mar 3, 2025, 06:54 Piotr P. Karwasz wrote: > Hi all, > > Configuration problems in our builde

Re: New committer: Jeff Thomas

Welcome aboard Jeff! Gary On Wed, Feb 26, 2025, 14:02 Piotr P. Karwasz wrote: > The Project Management Committee (PMC) for Apache Logging > has invited Jeff Thomas to become a committer and we are pleased > to announce that he has accepted. > > Please join us in welcoming Jeff to their new rol

Re: Anything left for 2.25.0?

Thank you for the update. Do you think it's possible to add a test to avoid regressions? Gary On Mon, Feb 3, 2025, 13:47 Volkan Yazıcı wrote: > Yes, see the `InternalLoggerRegistry` deadlock reported in #3399 > . The fix is ready > in > #34

Re: Can't see an apache link on google for log4jshell

> > Jan > > > On January 29, 2025 5:10:53 PM GMT+01:00, Gary Gregory > wrote: >> >> FYI. the page https://logging.apache.org/security.html does not use >> the string "log4jshell" anywhere, no wonder we don't come up on the >> first Google page

Can't see an apache link on google for log4jshell

FYI. the page https://logging.apache.org/security.html does not use the string "log4jshell" anywhere, no wonder we don't come up on the first Google page when searching for it. If I google "log4jshell apache", it's a little better with our security page in the middle of the first page. Gary

Re: Create artifacts for optional features

This all sounds very confusing to me. Using this scheme, I could create a set of dependencies on 2.x with empty jars that don't work on 3.x (because I picked the wrong jars). There is no way to verify that what I'm doing on 2.x will work on 3.x without trying it on 3.x, so... or am I missing someth

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

Ah... good one. I do rm my cache every couple months. I guess I'll have to do it more often! Gary On Tue, Dec 10, 2024, 11:46 AM Piotr P. Karwasz wrote: > Hi Gary, > > On 10.12.2024 17:18, Gary Gregory wrote: > > Here you go: > > > > diff tar

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

On Tue, Dec 10, 2024 at 9:17 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On 10.12.2024 14:58, Gary Gregory wrote: > > Here you go: > > > > mvn verify -Prelease artifact:compare > > -Dreference.repo=https://repository.apache.org/content/repositories/orgap

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

36 Gary On Tue, Dec 10, 2024 at 8:52 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On 10.12.2024 13:26, Gary Gregory wrote: > > Using: > > > > mvn verify -Prelease artifact:compare > > -Dreference.repo=https://repository.apache.org/content/repositories/orgap

Re: [DISCUSSION][VOTE] Release Apache Log4j 2.24.3 (RC1)

On Tue, Dec 10, 2024 at 8:23 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On 10.12.2024 13:23, Gary Gregory wrote: > > sh mvnw verify \ > >-Prelease artifact:compare \ > > > > -Dreference.repo=https://repository.apache.org/content/repositories/orgapa

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

og4j-bom-2.24.3.buildcompare [INFO] Any ideas? TY, Gary On Tue, Dec 10, 2024 at 7:23 AM Gary Gregory wrote: > > I'm following the review kit and I get: > > sh mvnw verify \ > -Prelease artifact:comp

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

I'm following the review kit and I get: sh mvnw verify \ -Prelease artifact:compare \ -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be compromised. Investigate or delete /User

Re: [VOTE] Release Apache Log4j 2.24.3 (RC1)

I'm following the review kit and I get: On Tue, Dec 10, 2024 at 6:31 AM Piotr P. Karwasz wrote: > > This is a vote to release the Apache Log4j `2.24.3`. > > Website: https://logging.staged.apache.org/log4j/2.24.3/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: 4aa5efec7f2e

Re: Problems creating custom appender using JPMS service in 3.0.0-beta3

t; have a single module with custom Log4j plugins. > > > On Dec 4, 2024, at 09:19, Gary Gregory wrote: > > > > I had to put some mysterious dot file in the root of my Maven module to > get > > my plugin to work. The only way I found this is by comparison with > anothe

Re: Problems creating custom appender using JPMS service in 3.0.0-beta3

I had to put some mysterious dot file in the root of my Maven module to get my plugin to work. The only way I found this is by comparison with another module but not all modules have this file. Gary On Wed, Dec 4, 2024, 8:16 AM Volkan Yazıcı wrote: > I agree with Pavel that users should only be

Re: Add JSpecify as `compile` dependency

The main issue with these annotations is that there are so many providers. It's so bad that tooling just now look for names like @NonNull _without considering the package name_, so there is no limit as to how much you end up with :-( On Mon, Dec 2, 2024 at 1:58 PM Matt Sicker wrote: > > I’m alrig

Re: PMC Meeting in December

Sounds 👍 good to me. Gary On Sun, Dec 1, 2024, 5:51 AM Piotr P. Karwasz wrote: > Hi all, > > I think we should have a PMC meeting in December to summarize what we > achieved in 2024. How does Sunday, 15th sound? > > A rapid draft of the agenda might be: > > * Status of Log4cxx. > > * Status of

Re: Compatibility between Log4j API and implementation

This is beyond confusing and a new kind of "soft" jar hell IMO. I read this twice and I have no idea how a user would make sense of this. Log4j 2.x should be all in sync, all jars should be released with each version and match. Period. IMO. Gary On Thu, Nov 28, 2024, 9:52 AM Piotr P. Karwasz w

Re: A logger config named "root"

This seems like a nice clean up that will break a lot of configurations. How about we issue a warning in 2.x like "The logger name 'root' is deprecated and will be removed in 3.0"? Gary On Tue, Nov 19, 2024, 7:01 AM Piotr P. Karwasz wrote: > Hi all, > > In Log4j Core 2 there is a residual sup

Re: [VOTE] Release Apache Log4j `2.24.2` (RC1)

On the macOS side +1 >From the src zip files: - ASC and SHA files OK - mvn clean verify OK Using: openjdk version "17.0.13" 2024-10-15 OpenJDK Runtime Environment Homebrew (build 17.0.13+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing) Apache Maven 3.9.9 (8e8579a9e76f

Re: Cleanup of `downloads.apache.org`

Hi all, Note that the statement on the EOL site is incorrect: "The reload4j project provides a drop-in replacement for Log4j 1.x with maintenance and security fixes." It certainly is not a "drop-in replacement" because it ripped out public classes and so breaks binary compatibility. It's more of

Re: Log4j release 2.24.1

Hi Piotr, Thanks for the details. The good new is that it was caught fairly quickly. Looking forward to reviewing the RC... Gary On Sat, Nov 16, 2024, 12:06 PM Piotr P. Karwasz wrote: > Hi Gary, > > On 16.11.2024 17:41, Gary Gregory wrote: > > [1]https://github.com/apache

Re: Log4j release 2.24.1

Hi All, Thank you Piotr for managing this release. [1] https://github.com/apache/logging-log4j2/issues/3143 This issue points to the merged PR https://github.com/apache/logging-log4j2/pull/2936, a large change set with zero tests. This isn't great since there are no tests to catch regressions :-

Re: Compatibility between Log4j API and implementation

d that log4j-api and log4j-core must use the > exact same version, could you add a version check that kicks in at class > initialization time, so that cursory testing is more likely to catch the > version mismatch? > > > On 2024/11/14 18:50:15 Gary Gregory wrote: > > I don

Re: Compatibility between Log4j API and implementation

I don't even want to try and explain that... it sounds backwards. I'll just keep everything nice and simple in my explanations to people: match is nice. Gary On Thu, Nov 14, 2024, 1:47 PM Ralph Goers wrote: > Log4j core has a version compatibility comparison just for this reason. If > core is u

Re: Compatibility between Log4j API and implementation

I think you keep it simple: versions must match. Versions that are unmatched are not supported. That's what I tell people at work and anyone who asks. Simple ;-) Gary On Thu, Nov 14, 2024, 5:25 AM Piotr P. Karwasz wrote: > Hi all, > > We usually recommend users to have a perfect version alignm

Re: Board report for November

Understood, thank you for the explanation. Gary On Tue, Nov 12, 2024, 7:18 AM Piotr P. Karwasz wrote: > Hi Gary, > > On 12.11.2024 12:49, Gary Gregory wrote: > > If we are going to mention components, shouldn't we also list Chainsaw? > > I could mention that the re

Re: Board report for November

If we are going to mention components, shouldn't we also list Chainsaw? Gary On Tue, Nov 12, 2024, 5:30 AM Piotr P. Karwasz wrote: > Hi all, > > Sorry for the short notice, but only today I found the time to prepare > the board report for November. > > Unless there are some remarks, I plan to

Re: [VOTE] Release Apache Log4j `3.0.0-beta3` (RC1)

+1 Finally builds all the way through. ASC OK, SHA512 OK. Gary On Sat, Nov 9, 2024 at 8:11 AM Gary Gregory wrote: > Hi All, > > Running: > > mvn clean verify -Dreference.repo= > https://repository.apache.org/content/repositories/orgapachelogging-1307 > -Prelease artif

Re: Flaky Rolling Appender tests

Hi Piotr, Thank you for your detailed comments. I'll try building again... until the build goes all the way through... Gary On Mon, Nov 11, 2024 at 12:11 PM Piotr P. Karwasz wrote: > Hi Gary, > > On 9.11.2024 14:11, Gary Gregory wrote: > > I get this failure: > >

Re: [VOTE] Release Apache Log4j `3.0.0-beta3` (RC1)

At the details link, you can see "Expecting actual not to be empty" and its stack trace. Gary On Sat, Nov 9, 2024, 3:46 PM Ralph Goers wrote: > Why doesn’t it say what the failure is? > > Ralph > > > On Nov 9, 2024, at 6:11 AM, Gary Gregory wrote: > > > &

Re: [DISCUSS][RESULT][VOTE] Release Apache Log4net 3.0.3

Well done then 👏 😀 Gary On Sat, Nov 9, 2024, 9:56 AM Jan Friedrich wrote: > Hi Gary, > > I released 3.0.3 on Thursday evening. > > Regards > > Jan > > > On November 9, 2024 1:39:17 PM GMT+01:00, Gary Gregory < > garydgreg...@gmail.com> wrote: > >&

Re: [VOTE] Release Apache Log4j `3.0.0-beta3` (RC1)

Hi All, Running: mvn clean verify -Dreference.repo= https://repository.apache.org/content/repositories/orgapachelogging-1307 -Prelease artifact:compare I get this failure: [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.963 s <<< FAILURE! -- in org.apache.logging.log4j

Re: [DISCUSS][RESULT][VOTE] Release Apache Log4net 3.0.3

Hi All, Is this vote still open? I can review it later today only. Gary On Thu, Nov 7, 2024 at 5:23 PM Jan Friedrich wrote: > Hello Piotr, > > you are right. The mail was addressed to me (and not the list). > I forwarded it to the list: > https://lists.apache.org/thread/b62547mgj6gzztd61k0m00m

Re: New API for log level manipulation

On Sat, Nov 2, 2024 at 11:15 PM Ralph Goers wrote: > > > > On Nov 2, 2024, at 3:51 PM, Piotr P. Karwasz > wrote: > > > > This would be the same setting as in Commons Logging, so I guess I would > be OK with that, if we keep an extension mechanism in the API. We could > probably split the impleme

Re: New API for log level manipulation

Hi Piotr, I would expect the LCD to allow LogManager.setLevel("com.gary.app", "debug") Having a Level version is OK as well. Gary On Thu, Oct 31, 2024, 1:25 PM Piotr P. Karwasz wrote: > Hi Gary, > > On 31.10.2024 17:12, Gary Gregory wrote: > > > &

Re: New API for log level manipulation

Good idea! One way I like to think about this is what is the API I need to build a tree view UI that shows the logger hierarchy where I can toggle levels for one logger or one logger tree (including the root). >set the configured level of a single logger Some people (like me) will want to enable

Discussion software

At some point, we were talking about discussion software and I brought up that other was beging discussed somewhere i could not find. It was on the com dev list (https://lists.apache.org/list.html?d...@community.apache.org) and is being tracked here: https://cwiki.apache.org/confluence/x/KYqMEw G

Re: [REVIEW] Apache Log4net 3.0.2 (was [VOTE] Release Apache Log4net 3.0.2)

Hi Jan, Yes, I have gpg on Windows. I'm just looking for idiot-proof instructions for someone who isn't a .NET expert ;-) Gary PS: Win11 is on the horizon here. On Fri, Oct 18, 2024, 12:21 PM Jan Friedrich wrote: > Hello Gary, > > your company will have to solve this by the end of 2025 ;-) > >

Re: [VOTE] Release Apache Log4cxx 1.3.0

I think it's a bit confusing to have both 256 and 512 sha files. We shouldn't imo give the impression that you should check both. One is plenty imo, 512. Gary On Wed, Oct 16, 2024, 7:05 AM Robert Middleton wrote: > Notes(none of these are blockers): > * Fuzzing page doesn't render > correctly(h

Re: Successor to mailing lists

This is one item I would like us, Apache, spend our money on. Gary On Tue, Oct 15, 2024, 12:33 PM Matt Sicker wrote: > Yeah this sounds like what Volkan discovered in his research. The mailing > list software is fucking up the metadata in such a way as to make it > invalid in various spam check

Re: [log4j] Using `DateTimeFormatter` by default

That's quite a difference! Why would we make things deliberately slower? Gary On Mon, Oct 14, 2024, 4:57 PM Ralph Goers wrote: > Wow. I didn’t expect them to be that much faster. That makes me very > reluctant to be ok with switching. > > Ralph > > > > > On Oct 14, 2024, at 1:51 PM, Volkan Ya

Re: Successor to mailing lists

I'll admit that I rely on PonyMail. It seems we (Apache) should have a professional (paid for is ok) set up for this, not a custom solution. Gary On Mon, Oct 14, 2024, 3:51 PM Ralph Goers wrote: > Maybe we just need to start contributing to PonyMail to improve the UI to > eliminate actually nee

Re: Feature proposal for a new Filter result: Throw

On Thu, Oct 10, 2024 at 4:09 AM Piotr P. Karwasz wrote: > Hi Gary, > > On Wed, 9 Oct 2024 at 16:34, Gary D. Gregory wrote: > > My proposal is to allow a user to _not_ define any custom filters by > reusing a new Result enum value called “Throw”. When a filter returns > “Throw”, then Log4j throws

Re: Successor to mailing lists

On Fri, Oct 11, 2024 at 2:08 PM Christian Grobmeier wrote: > > > On Fri, Oct 11, 2024, at 19:35, Gary Gregory wrote: > > I'm not crazy about having to bounce around sections of various repos in > > addition to monitoring emails, which has to be done anyway. It'

Re: Successor to mailing lists

t; -Robert Middleton > > > > On Thu, Oct 10, 2024 at 9:44 AM Volkan Yazıcı > > wrote: > > > > > > GitHub can be configured to send email notifications. We can route > these > > > to, say, `notificati...@logging.apache.org` email address to have our >

Re: Successor to mailing lists

tween the projects. > > -Robert Middleton > > On Thu, Oct 10, 2024 at 9:44 AM Volkan Yazıcı > wrote: > > > > GitHub can be configured to send email notifications. We can route these > > to, say, `notificati...@logging.apache.org` email address to have our > loca

Re: Successor to mailing lists

I thought this was recently discussed on @members, but now I can't find the thread! I'm not even sure if it was on @members, which exemplifies the scaling problem discussed on the list, among other issues: When you look at PonyMail's UI, there are about 60 internal mailing lists under the ' apache.

Re: Feature proposal for a new Filter result: Throw

tead of the throw then I could understand what you are saying. > > Ralph > > > > On Oct 9, 2024, at 9:55 AM, Gary Gregory wrote: > > > > Hi Ralph, > > > > Thank you for taking a peek. > > > > I either did not explain myself clearly or in enough detail

Re: Feature proposal for a new Filter result: Throw

Hi Ralph, Thank you for taking a peek. I either did not explain myself clearly or in enough detail as I don't feel you fully grasped what I proposed ;-) "Secondly, I don’t like that the only criteria it is able to use to determine whether to throw an exception is the log level." It is _not_ onl

Re: Feature proposal for a new Filter result: Throw

Hi Volkan, Thank you for your review. Later, I would like to have our whole build check all tests for Hibernate warnings. Today, I'm taking a first step. The second step is to have another Maven module's tests perform this check. Recasting the solution as a JUnit 5 extension is a good idea, but

Re: [VOTE] Move Flume to dormant

FWIW, I don't think apache voting guidelines allow for "you can only vote a certain way only if ..." Gary On Wed, Oct 2, 2024, 3:30 PM Christian Grobmeier wrote: > Hello everyone, > > We have discussed this in the past. I hope we can pick up a decent dev > speed with Flume after we adopt it. I

Re: [RESULT][VOTE] Release Apache Log4net 3.0.1

Jan, If the vote says 72 hours, you should wait 72 hours before counting votes and releasing ;-) Gary On Fri, Sep 27, 2024, 3:43 AM Fred am Nil wrote: > Hi, > > and here is my +1. > > With that the vote passed with 3 +1 votes from Davyd McColl, Christian > Grobmeier and myself. > I will contin

Re: [VOTE] Release Apache Log4j `2.24.1` (RC1)

I expected to see SBOMs in the binary zip, CycloneDX and/or SPDX. Are they missing? Did I not find them? Gary On Tue, Sep 24, 2024 at 3:13 PM Piotr P. Karwasz wrote: > > This is a vote to release the Apache Log4j `2.24.1`. > > Website: https://logging.staged.apache.org/log4j/2.24.1/index.html >

Re: [VOTE] Release Apache Log4j `2.24.1` (RC1)

+1 passes on macOS, fails on Windows as usual (see GH issues). I tested the src zip file. - ASC file OK - SHA-512 file OK - `mvn clean verify` OK Environment: openjdk version "17.0.12" 2024-07-16 OpenJDK Runtime Environment Homebrew (build 17.0.12+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0

Re: Use RTC in Log4j and Log4Net

This proposal is two pages (on my phone)! I can't imagine counting lines and walking through these steps, it's crazy making IMO. How would you count lines anyway? From diff output? I'd rather skip the bikeshedding and let devs create PRs when they think it makes sense. IOW, when they want a review

Re: Use RTC in Log4j and Log4Net

I'm with Matt. It should be left at the discretion of the developer whether a PR or straight commit is justified. I see no reason to throw sand in the gears. Gary On Tue, Sep 17, 2024, 2:05 PM Matt Sicker wrote: > I’m -1 on switching to RTC. Same reason as always. Losing momentum from > waiting

Re: Use RTC in Log4j and Log4Net

Maybe we should talk about net vs. J separately? Gary On Tue, Sep 17, 2024, 10:53 AM Piotr P. Karwasz wrote: > Hi Ralph, > > On Tue, 17 Sept 2024 at 15:47, Ralph Goers > wrote: > > > > Why? i.e. - what currently isn’t working? > > I merely wish to formalize what is already happening and set up

Re: [VOTE] Release Apache Log4net 3.0.0

Ah, thank you. Gary On Mon, Sep 16, 2024, 9:50 AM Jan Friedrich wrote: > Hi Gary, > > please see > https://lists.apache.org/thread/v8kyxz7zdvp3cypo1506yflk3bbvysym > > I did not change the subject to [RESULT]. > > Regards. > > Jan > > On 16 September 2024

Re: [VOTE] Release Apache Log4net 3.0.0

I don't think I saw a [RESULT] message with a tally of the result. Gary On Sun, Sep 15, 2024 at 3:26 PM Davyd McColl wrote: > > Hi > > Apologies for the late response. FWIW, my +1 too. > > -d > > > On 15 September 2024 20:59:13 Jan Friedrich wrote: > > > Hi, > > > > and here is my +1. > > > > W

Re: [VOTE] Release Apache Log4j `2.24.0`

Volcan, Please stop complaining about the hours I've already sunk into validation on 3 different operating system on two different machines. You're not helping the cause. I can't help but notice the irony that one of the failures is in the "reproducible" part of the build. >From my point of view

Re: (logging-parent) branch main updated: Modify review kit

Why doesn't the maven build in the review kit (below) invoke clean goal? Gary On Tue, Sep 3, 2024, 11:37 AM wrote: > This is an automated email from the ASF dual-hosted git repository. > > pkarwasz pushed a commit to branch main > in repository https://gitbox.apache.org/repos/asf/logging-parent

Re: [VOTE] Release Apache Log4j `2.24.0`

Thank you Piotr! Gary On Tue, Sep 3, 2024, 11:17 AM Piotr P. Karwasz wrote: > Hi all, > > On Sat, 31 Aug 2024 at 21:30, Piotr P. Karwasz > wrote: > > > > This is a vote to release the Apache Log4j `2.24.0`. > > > > Website: https://logging.staged.apache.org/log4j/2.24.0/index.html > > GitHub:

Re: [VOTE] Release Apache Log4j `2.24.0`

xception [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :log4j-api-test Gary On Sun, Sep 1, 2024 at 7:11 PM Gary Gregory wrote: > > On Sun, Sep 1, 2024 at 6:01 PM Piotr P. Karwasz > wrote: > > > > Hi Gary, > &g

Re: [VOTE] Release Apache Log4j `2.24.0`

On Sun, Sep 1, 2024 at 6:01 PM Piotr P. Karwasz wrote: > > Hi Gary, > > On Sun, 1 Sept 2024 at 23:34, Gary Gregory wrote: > > Now I get: > > > > [INFO] Results: > > [INFO] > > [ERROR] Failures: > > [ERROR] NetUtilsTest.testCanonicalHostName:7

Re: [VOTE] Release Apache Log4j `2.24.0`

On Sun, Sep 1, 2024 at 5:09 PM Piotr P. Karwasz wrote: > > Hi Gary, > > On Sun, 1 Sept 2024 at 23:00, Piotr P. Karwasz > wrote: > > On Sun, 1 Sept 2024 at 22:44, Gary Gregory wrote: > > > [ERROR] sha512 mismatch log4j-bom-2.24.0-cyclonedx.xml: investigate >

Re: [VOTE] Release Apache Log4j `2.24.0`

Hi All, Thank you Piotr for preparing the RC. Using the review kit, this is what I get on the step 'sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO' [INFO] --- artifact:3.5.1:compare (default-cli) @ log4j-bom --- [WARNING] property is inherited, it should be defined in po

Re: [Discuss][VOTE] Release Apache Log4j `2.24.0`

I've not looked at details but Ralph's comment hints that we need to explain to users how to migrate if it's anything more than an import change. WDYT? Gary On Sat, Aug 31, 2024, 5:06 PM Ralph Goers wrote: > The API section has > > Thread Context is mostly superseded by Scoped Context, which, u

Re: Delaying publication of `log4j-flume-ng` in 3.x

Hi, I'd like to follow Ralph's lead on Flune related topics. Gary On Thu, Aug 29, 2024, 8:12 AM Piotr P. Karwasz wrote: > Hi all, > > The `log4j-flume-ng` module _de facto_ contains 3 different appenders: > > * an Avro appender, that only depends on Avro and Avro IPC. Since it > only communica

Re: Open GitHub discussions for Log4j Scala and Kotlin

In fact, it's been broken for ages: when you click on a gitbox repo, it redirects to github! It should instead display its UI as it did in the past... Gary On Wed, Aug 14, 2024, 10:58 AM Gary Gregory wrote: > Gitbox is just a very thin UI on top of git, no PRs. > > Gary > &g

Re: Open GitHub discussions for Log4j Scala and Kotlin

t. > > > > There might also be parts of the world where GH is not available but > Apache > > servers are (more of a geopolitical issue). > > > > Gary > > > > On Wed, Aug 14, 2024, 3:43 AM Piotr P. Karwasz > > wrote: > > > >> Hi Gary,

Re: Open GitHub discussions for Log4j Scala and Kotlin

Gmail behaves differently based on the platform. Gary On Wed, Aug 14, 2024, 7:24 AM Piotr P. Karwasz wrote: > Hi Gary, > > On Wed, 14 Aug 2024 at 12:34, Gary Gregory wrote: > > I think that to "deactivate" the mailing lists you refer to would be very > > bad and

Re: Open GitHub discussions for Log4j Scala and Kotlin

14, 2024, 3:43 AM Piotr P. Karwasz wrote: > Hi Gary, > > On Fri, 9 Aug 2024 at 12:15, Gary Gregory wrote: > > While it is a different community, I have received negative feedback in > > Commons against the trend to spread information all over the place, and > we > > don&#x

Re: Release timeline for log4j 2.24.0?

Isn't that assertable from a unit test? Gary On Tue, Aug 13, 2024, 6:00 PM Ralph Goers wrote: > Piotr, I am still concerned that you never looked into the issues I had > with StringArrayThreadContextMap. My performance tests were showing that it > was fast because it wasn’t actually setting val

Re: Release timeline for log4j 2.24.0?

John, You should test our snapshot builds just in case ;-) Gary On Tue, Aug 13, 2024, 3:43 PM Piotr P. Karwasz wrote: > Hi John, > > On Tue, 13 Aug 2024 at 21:10, John Engebretson > wrote: > > HI - just curious when the updated ThreadContextMap will be available? > > The latest release is 2

Re: Staging site

Hi, Does the tech we use to build/host allow for the inclusion of a search box, say at the top? Javadoc now includes a search box which is quite a nice feature IMO. Gary On Fri, Aug 9, 2024 at 3:02 AM Piotr P. Karwasz wrote: > > Hi all, > > We finished revamping the documentation of Log4j 2. Th

Re: Staging site

On the front page: "Batteries included" Err... what? Let's not get cute here please. Gary On Fri, Aug 9, 2024 at 3:02 AM Piotr P. Karwasz wrote: > > Hi all, > > We finished revamping the documentation of Log4j 2. The result is > available on the staging site: > > https://logging.staged.apache.or

  1   2   3   4   5   6   7   8   9   10   >