Ralph, thank you.
Why did you create a new repository?
AFAIK, infra could reopen the old one on request.
Vladimir
understand now. thanks.
XenoAmess
From: Apache
Sent: Thursday, December 23, 2021 2:45:14 PM
To: dev@logging.apache.org
Subject: Re: New Log4j 1 repo
https://github.com/apache/log4j was read-only. The new repo is not.
Ralph
> On Dec 22, 2021, at 11:34 PM, Ralph
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 plug
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 t
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
> 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 guess
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, D
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,
rig
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 co