You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/01/31 12:26:00 UTC
[jira] [Commented] (LOG4J2-3381) Programmatically configuring Log4j2
[ https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484639#comment-17484639 ]
Gary D. Gregory commented on LOG4J2-3381:
-----------------------------------------
You can try 2.17.2-SNAPSHOT where I recently added support for this API. I would be good to know if the SNAPSHOT works for your use case.
> Programmatically configuring Log4j2
> -----------------------------------
>
> Key: LOG4J2-3381
> URL: https://issues.apache.org/jira/browse/LOG4J2-3381
> Project: Log4j 2
> Issue Type: Question
> Reporter: Jitin Dominic
> Priority: Major
>
> During upgrading log4j2 in grails 2.5.4 application, I removed all log4j 1.2.17 dependencies and added following dependencies pertaining to v2.17.1:
> * log4j-api
> * log4j-core
> * log4j-1.2-api
> * log4j-slf4j-impl
>
> I'm trying to read my _log4j2.properties_ file programmatically. We are using PropertyConfigurator.configure() to configure the logger.
>
> But I noticed in the [documentation|https://logging.apache.org/log4j/2.x/manual/migration.html] that Log4j 1.x bridge has some limitations and we can't use it for programmatic configuration.
> Is there any alternative way to configure logger programmatically without using PropertyConfigurator?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)