As its name implies, ConfigurationBuilder creates a new Configuration. Any
Configuration you build this way would replace an existing Configuration.
I’d like to understand your use case for wanting Programmatic configuration. If
you need to do that either we need to implement some feature so
When using ConfigurationBuilder is it all or nothing or can you integrate what
your builder builds into the existing log4j that’s already been initialized
from log4j.xml. Actually I’ve already initialized using my xml “manually” using
setConfigLocation earlier.
With 1.x you can get a reference
We just released 2.17.2 which contain many improvements to the 1.2 bridge.
Would you give it a try?
Gary
On Wed, Mar 2, 2022, 12:38 Natasha D'Silva wrote:
> I’m using log4j v2, the log4j v1 bridge and a v1 log4j.properties file
> that specifies an appender like this:
>
>
>
>
I'm using log4j v2, the log4j v1 bridge and a v1 log4j.properties file that
specifies an appender like this:
log4j.appender.KRFTRACE=${abc.def.log4j.appender.KRFTRACE}
log4j.rootLogger=ALL, KRFTRACE
I set the system property abc.def.log4j.appender.KRFTRACE to the appropriate
class.
Hello everyone,
I have the following requirements for the migration of a custom log4j1
RollingFileAppender:
* Log every morning into a new directory with the current date as the name
of the directory and part of the log file name
* If the size of a log file exceeds 100 MB, rollover to
