Re: [Discuss][VOTE] Deprecation of 2.x modules/features and removal in 3.x

Rats. In my first sentence replace “modules” with “repos”. Ralph > On Oct 31, 2023, at 3:53 PM, Ralph Goers wrote: > > Christian, > > Deprecation and moving to separate modules are not the same thing at all. I > would be +1 to moving everything on this list that isn’t outright removed to > s

Re: Why is JNDI still necessary?

There is a difference between a JEE application that only uses servlets vs one that uses EJBs. At a former employer we often used JBoss to run servlets even though we had no EJBs. In an environment with EJBs I am not sure how you can distinguish the various components from each other without JND

[Discuss][VOTE] Deprecation of 2.x modules/features and removal in 3.x

Christian, Deprecation and moving to separate modules are not the same thing at all. I would be +1 to moving everything on this list that isn’t outright removed to separate repos. I have stated that several times. Gary is strongly against doing that. If you are somehow equating deprecation wi

Re: Why is JNDI still necessary?

I’m not sure how much people use this deployment model anymore, but JNDI was and still is at the core of JavaEE (now JakartaEE) dependency injection APIs. While CDI is the current way of using dependency injection there, CDI is compatible with JNDI and the other JavaEE tech that came in between

Re: Why is JNDI still necessary?

Piotr, I think it is important to differentiate what is a requirement and what is just another way of achieving something. My employer has several Tomcat- and JBoss-based JEE applications (using Log4j) and we don't have a single JNDI usage I know of. I would like to hear "the functional need" that

Re: Why is JNDI still necessary?

Hi Christian, On Tue, 31 Oct 2023 at 21:57, Christian Grobmeier wrote: > I am surprised we still have JNDI in the code at all, but this made me > curious: > why do JEE users need JNDI features for logging? Why can't they just use the > normal log mechanism? JNDI is basically a bean container/f

Re: [VOTE] Deprecation of 2.x modules/features and removal in 3.x

+1 to all - deprecation to me means we add a label that we plan to remove it in 3.x, but we are not removing it not. We can step back. Many of those modules don't look as if they need to belong in the main repo. I can accept kubernetes/docker stuff, but not in the main repo. I have a strong +1

Why is JNDI still necessary?

Hi, on the recent deprecation vote I saw this vote (from Ralph): > * JNDI-related features: -1 Unfortunately, JEE users require this. I am surprised we still have JNDI in the code at all, but this made me curious: why do JEE users need JNDI features for logging? Why can't they just use the norm

Re: [VOTE] Deprecation of 2.x modules/features and removal in 3.x

Here are my votes: > On Oct 30, 2023, at 1:44 AM, Piotr P. Karwasz wrote: > > This is a vote to deprecate the following `2.x` modules and features > and remove them from the `3.x` release: > > * `log4j-cassandra`: +1 > * CouchDB appender: +1 > * `log4j-docker` -1 - Still useful and supportable

Re: Project activity monitor

I can, but I prefer you doing it. It is good for sharing the know-how. (Let me know if you want me to do it.) 1. Add `log4j-server` entry to the `proj-spec` matrix in `update-stats.yaml`

Re: Project activity monitor

Hi Volkan, On Tue, 31 Oct 2023 at 12:07, Volkan Yazıcı wrote: > > I have set up a page sharing statistics about all Logging Services > projects: https://logging-activity-monitor.staged.apache.org/ There you can > find activity data collected from GitHub repositories for all projects: > Log4j, Cha

Project activity monitor

I have set up a page sharing statistics about all Logging Services projects: https://logging-activity-monitor.staged.apache.org/ There you can find activity data collected from GitHub repositories for all projects: Log4j, Chainsaw, Log4Net, Log4cxx, etc. Since the `logging-site` repository is pret