[ 
https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484651#comment-17484651
 ] 

Jitin Dominic edited comment on LOG4J2-3381 at 1/31/22, 1:05 PM:
-----------------------------------------------------------------

[~ggregory] 

Just to confirm, so I need to just change the dependency for _log4j-1.2-api_ 
only?

And to include that in gradle, I'll be adding this:

 
{code:java}
compile group: 'org.apache.logging.log4j', name: 'log4j-1.2-api', version: 
'2.17.2-SNAPSHOT' {code}
 

*Update:*

I tried the update, but since the snapshot not released, so it throws 
exception. Could you tell me which repository I need to add exactly to check 
this.


was (Author: JIRAUSER283874):
[~ggregory] 

Just to confirm, so I need to just change the dependency for _log4j-1.2-api_ 
only?

And to include that in gradle, I'll be adding this:

 
{code:java}
compile group: 'org.apache.logging.log4j', name: 'log4j-1.2-api', version: 
'2.17.2-SNAPSHOT' {code}
 

 

> 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)

Reply via email to