Re: Deprecating modules in 2.x

2023-09-11 Thread Volkan Yazıcı
I would be in favor of deprecating the following modules in `2.x` and dropping them starting from `3.0.0`: 1. `log4j-jndi` (available only in `main`) – nobody should use JNDI anyway 2. `log4j-layout-jackson*` – `JsonTemplateLayout` succeeds `JsonLayout`, I doubt if anybody is using `Xm

Re: Deprecating modules in 2.x

2023-09-11 Thread Gary Gregory
FWIW, I need all JDBC modules. Gary On Mon, Sep 11, 2023 at 4:00 AM Volkan Yazıcı wrote: > > I would be in favor of deprecating the following modules in `2.x` and > dropping them starting from `3.0.0`: > >1. `log4j-jndi` (available only in `main`) – nobody should use JNDI >anyway >2.

Re: Deprecating modules in 2.x

2023-09-11 Thread Gary Gregory
We also use the CSV module (but only in some of our tests.) Gary On Mon, Sep 11, 2023 at 7:07 AM Gary Gregory wrote: > > FWIW, I need all JDBC modules. > > Gary > > On Mon, Sep 11, 2023 at 4:00 AM Volkan Yazıcı wrote: > > > > I would be in favor of deprecating the following modules in `2.x` and

Re: Deprecating modules in 2.x

2023-09-11 Thread Piotr P. Karwasz
Hi Volkan, On Mon, 11 Sept 2023 at 10:00, Volkan Yazıcı wrote: > > I would be in favor of deprecating the following modules in `2.x` and > dropping them starting from `3.0.0`: > >1. `log4j-jndi` (available only in `main`) – nobody should use JNDI >anyway >2. `log4j-layout-jackson*` –

Re: [VOTE] Release Apache Logging Parent 10.0.0 (RC4)

2023-09-11 Thread Gary Gregory
I don't think a parent pom requires busy work like a format vote. See the board thread (if you have proper PMC access): https://lists.apache.org/thread/k15gco2snsf9dsfkznp6289msn4vroq8 See my comment here https://lists.apache.org/thread/fc6c0mvpjn4y6sw0kymqm3vjr4kr8obw Gary On Fri, Sep 8, 2023 a

Re: [VOTE] Release Apache Logging Parent 10.0.0 (RC4)

2023-09-11 Thread Matt Sicker
+1 > On Sep 8, 2023, at 9:07 AM, Volkan Yazıcı wrote: > > This is a vote to release the Apache Logging Parent 10.0.0 (RC4). > > Source repository: https://github.com/apache/logging-parent > Commit: 2af643f84ada9a05e08229d077c6fafee2fed732 > Distribution: https://dist.apache.org/repos/dist/dev/l

Re: Deprecating modules in 2.x

2023-09-11 Thread Matt Sicker
The Kubernetes and Docker plugins are for additional lookup variables, though based on how I’ve used Kubernetes at least (like via Kustomize, Helm, Spinnaker, and general YAML template tooling), I’ve relied mostly on binding anything relevant from the manifest into environment variables. > On S

Re: Deprecating modules in 2.x

2023-09-11 Thread Ralph Goers
I wrote the Docker and Kubernetes stuff for anyone who wants to bypass writing to the console and still have the environment variables captured. Ralph > On Sep 11, 2023, at 9:40 AM, Matt Sicker wrote: > > The Kubernetes and Docker plugins are for additional lookup variables, though > based o

Re: [VOTE] Release Apache Logging Parent 10.0.0 (RC4)

2023-09-11 Thread Christian Grobmeier
+1 On Fri, Sep 8, 2023, at 16:07, Volkan Yazıcı wrote: > This is a vote to release the Apache Logging Parent 10.0.0 (RC4). > > Source repository: https://github.com/apache/logging-parent > Commit: 2af643f84ada9a05e08229d077c6fafee2fed732 > Distribution: https://dist.apache.org/repos/dist/dev/logg

Re: Framework for integration tests

2023-09-11 Thread Matt Sicker
Testcontainers is really neat, but it does require Docker, so I’m not sure how to best use it in CI (particularly outside Linux). Arquillian is a classic option that’s been around for as long as I’ve been using Java for server-side anything, though I never really figured out how to use it (it se

Re: [log4j] Moving JMX GUI to its own repo

2023-09-11 Thread Matt Sicker
I’d be alright with this. Considering the fact that we’d rather use JFR in 3.x for metrics-related stuff, offloading JMX stuff makes sense (especially a JConsole extension like this). > On Sep 8, 2023, at 5:00 AM, Volkan Yazıcı wrote: > > I have created a dedicated repository for the `log4j-jm