Re: [log4cxx] Next steps / release?

On Thu, Dec 29, 2022 at 05:21:34PM -0500, Robert Middleton wrote: > With some fixes that have been accomplished over the past few weeks, > we now have only 1-2 issues in JIRA that would need to be finished for > a release, and I think both of those are effectively done at this > point. > > I'm pre

Re: Maven site failure

> On Dec 29, 2022, at 5:44 PM, Ralph Goers wrote: > > I am trying to build the web site and it is failing in the javadoc plugin in > log4j-layout-template-json-test because there are public or protected classes > to document. Either the javadoc plugin needs to be disabled for the module or

Maven site failure

I am trying to build the web site and it is failing in the javadoc plugin in log4j-layout-template-json-test because there are public or protected classes to document. Either the javadoc plugin needs to be disabled for the module or some classes need to be made public. Ralph

Re: [log4cxx] Next steps / release?

I think the next_stable branch should be released now. I am not aware of any issue that would prevent a release. I will do some more tests with production code this weekend to ensure there is no anything I have missed. On Fri, Dec 30, 2022 at 9:21 AM Robert Middleton wrote: > With some fixes t

[log4cxx] Next steps / release?

With some fixes that have been accomplished over the past few weeks, we now have only 1-2 issues in JIRA that would need to be finished for a release, and I think both of those are effectively done at this point. I'm pretty happy with where things are at the moment - there's always more tweaking t

Re: Log4Net 2.014

Rupak and Kevin, Please note that your emails contain a classification that these are internal Schwab emails but that you have sent them to a public mailing list. We obviously ignore such classifications since there is no way to make them private once you have done that. I can’t comment on you

Re: Log4Net 2.014

HI @Tools Support is there any ways to have this work being escalated as this impacted production stability and damaging the logging server in Production SNE environment From: Gardenhire, Kevin Date: Thursday, December 29, 2022 at 2:12 PM To: dev@logging.apache.o

Log4Net 2.014

Hi, We recently upgraded our Log4Net package from 1.2.13 to 2.0.14 to remediate a security flaw found in the old package. After upgrading we have found an issue that is not allowing 2 instances of an application to write to the same file location. We have a blue/green pool deployment strategy w

Re: [log4j] Question about the initial configuration created in LoggerContext

Yeah, I think you’re right, Ralph. Thanks for reasoning this over with me. Returning quickly is still a good idea. — Matt Sicker > On Dec 29, 2022, at 01:16, Ralph Goers wrote: > > The reason a DefaultConfiguration is created and NOT the identified > configuration is that a) we would have to

Re: [log4j] The grand infra revamp

Daniel Gruno stated in INFRA-23996 that they will implement the ticket in a couple of days, I will wait for a week. You can go ahead and merge your changes with necessary `changes.xml` modifications, just like what we have done before. I will take care of resolving `changes.xml`-related merge conf