Re: New Log4j 1 repo

2021-12-22 Thread Vladimir Sitnikov
Ralph, thank you. Why did you create a new repository? AFAIK, infra could reopen the old one on request. Vladimir

Re: New Log4j 1 repo

2021-12-22 Thread Apache
https://github.com/apache/log4j was read-only. The new repo is not. Ralph > On Dec 22, 2021, at 11:34 PM, Ralph Goers wrote: > > I have cloned the read-only log4j repo to > https://github.com/apache/logging-log4j1. > > I have followed the build instructions and had to modify the javadoc

Re: New Log4j 1 repo

2021-12-22 Thread Xeno Amess
Do read only mean we cannot give pull request? Then how can I help you clean the pom correct... XenoAmess From: Ralph Goers Sent: Thursday, December 23, 2021 2:34:02 PM To: dev@logging.apache.org Subject: New Log4j 1 repo I have cloned the read-only log4j repo

New Log4j 1 repo

2021-12-22 Thread Ralph Goers
I have cloned the read-only log4j repo to https://github.com/apache/logging-log4j1. I have followed the build instructions and had to modify the javadoc plugin to not fail on errors. Now it fails in the site plugin. If someone else wants to take this on I would suggest the first PR should just

Re: LOG4J2-3243

2021-12-22 Thread Ralph Goers
> On Dec 22, 2021, at 9:20 AM, Volkan Yazıcı wrote: > > Ralph, mind elaborating a bit more on what the exact problem is, please? > `log4j.configuration` gets detected, log4j-1.2-api (provided by Log4j 2) > kicks in, and tries to load the Log4j 1 configuration. This sounds okay to > me. I

Re: LOG4J2-3243

2021-12-22 Thread Carter Kozak
Is the case that the log4j2 log4j-1.2-api is not on the classpath, but log4-1.2 itself is? Ideally we could detect that case and allow log4j1 to do its thing, but that's easier said than done outside of standard cases (for instance when interesting plugin/webapp classloaders are used) On Wed,

Re: LOG4J2-3243

2021-12-22 Thread Volkan Yazıcı
Ralph, mind elaborating a bit more on what the exact problem is, please? `log4j.configuration` gets detected, log4j-1.2-api (provided by Log4j 2) kicks in, and tries to load the Log4j 1 configuration. This sounds okay to me. I guess it gets messed up when an application uses both Log4j 1 and 2,

Re: LOG4J2-3243

2021-12-22 Thread Ralph Goers
Volkan pointed out that the issue number in the subject was wrong. Ralph > On Dec 21, 2021, at 10:30 PM, Ralph Goers wrote: > > This ticket complains because ConfigurationFactory looks to see if a system > property named log4j.configuration is set. > If it is then it tries to initialize the