Re: [log4j] Unstable tests on Windows

Yesterday I disabled one and created #2011 (labeled with `tests`) for it. You can navigate all `tests` labeled issues or simply search for `@DisabledOnOs` in the code base – there are not

Re: [log4j] Unstable tests on Windows

Hi Ralph, On Tue, 28 Nov 2023 at 06:01, Ralph Goers wrote: > > I would be -1 if the issues are going to be ignored or not tracked in any > way. I don’t know if GitHub has something like a Jira Epic or if they can be > tagged in some way so that they can be easily located but something like that

[log4j] Releasing Log4j `3.0.0`

I plan to work on `main` until February, finalize recycler implementation, carry out whatever improvement I can, and release `3.0.0`. *If you have any objections with this plan, or if you have things to do on `main` and you cannot comply with this schedule, etc., let's discuss.* I want to agree on

Re: [log4j] Releasing Log4j `3.0.0`

Hi Volkan, On Tue, 28 Nov 2023 at 11:20, Volkan Yazıcı wrote: > *Personal remark:* I am against releasing `3.0.0` from `main`. `2.x` > changes that didn't go into `main` are titanic. `main` also contains > several incomplete code, doc, or both. I support the idea of forking `3.x` > from `2.x`, ba

Re: [log4j] Unstable tests on Windows

I think JUnit can group tests in categories with annotations (AFK). Gary On Tue, Nov 28, 2023, 12:01 AM Ralph Goers wrote: > I would be -1 if the issues are going to be ignored or not tracked in any > way. I don’t know if GitHub has something like a Jira Epic or if they can > be tagged in some

Re: [log4j] Releasing Log4j `3.0.0`

I'm OK with either direction for merges for anything between 2.x and 3.x branches for now and certainly until 3.x makes it out as a release. I won't argue for or against either. As a semi aside, in Commons, I circumvented the whole JPMS garbage, its split module horror show for tests by letting th

Re: [log4j] Releasing Log4j `3.0.0`

> On Nov 28, 2023, at 7:21 AM, Gary Gregory wrote: > > I'm OK with either direction for merges for anything between 2.x and 3.x > branches for now and certainly until 3.x makes it out as a release. I won't > argue for or against either. > > As a semi aside, in Commons, I circumvented the whol

Re: [log4j] Releasing Log4j `3.0.0`

I do not understand what my email provider has against Volkan. Once again I did not receive his email. Looking at the archive I see you want to release 3.0.0 in February. That may be possible but that isn’t exactly what was discussed in the last video meeting we had. The meeting notes are at

Re: [log4j] Releasing Log4j `3.0.0`

Okay. I will do the next beta release sometime this week. We can do more as we see fit. On Tue, 28 Nov 2023 at 15:59, Ralph Goers wrote: > I do not understand what my email provider has against Volkan. Once again > I did not receive his email. > > Looking at the archive I see you want to release

[chainsaw] Next steps? Or is it over?

Hello, I have started to clean up a few things that seemed good to me. The last time I sent a message like this was 1.5 months ago, but there was not much progress in maintaining it. I am currently in a state where I slowly get what should be happening, but unfortunately, it does not. We are n

Re: [chainsaw] Next steps? Or is it over?

I have dropped the ball here, but will commit to working on this, this year. I want to preserve a bunch of what can be done in the https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep branch, and some of that just isn't possible because equivalent functionality was never added

Re: [chainsaw] Next steps? Or is it over?

Hi Scott, I believe you; thanks for speaking up and being around. How can I help? I think Chainsaw needs to see a release soon, so what can I do to help you? I am glad to clean up things and whatever is necessary. Kind regards, Christian On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote: > I

Re: [chainsaw] Next steps? Or is it over?

I've fixed the logger tree split pane UI (left artifacts when you drag), and I've added VFSLogFilePatternReceiver support and it works fine. To test VFSLogFilePatternReceiver: * Start Chainsaw * View, Show Receivers menu * Hit the 'create' icon in the receivers pane * Select 'New VFSLogFilePattern