On Fri, Jan 7, 2022 at 12:10 PM Ted Dunning wrote:
> I have been watching the private and public mailing lists for Apache
> Logging as part of $dayjob as well.
>
> I read the mood there differently. The most recent comment I remember was a
> confirmation that "no bugfixes or security patches are
I have been watching the private and public mailing lists for Apache
Logging as part of $dayjob as well.
I read the mood there differently. The most recent comment I remember was a
confirmation that "no bugfixes or security patches are planned for log4j1".
Log4j2 really is much larger than necess
Thanks Chris, et. al. I have been monitoring this thread already, but I
appreciate you following up. :-)
I checked out the log4j2 source repo as part of my remediation efforts
inside my employer. tbh I was/am shocked at the amount of code and esp the
number of dependencies, for something that shou
I just noticed that Patrick commented on ZOOKEEPER-2342 expressing doubt
about sticking with Log4J, so I want to make sure his perspective gets
included in our thread here. Specifically added him to the To: line.
Chris Nauroth
On Thu, Jan 6, 2022 at 11:16 PM Enrico Olivelli wrote:
> I believe
Shivakumar created ZOOKEEPER-4439:
-
Summary: Upgrade jetty-server and jetty-servlet
Key: ZOOKEEPER-4439
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4439
Project: ZooKeeper
Issue Typ
