logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-998) Make org.apache.logging.log4j.core.Logger#updateConfiguration protected
Date Sat, 25 Apr 2015 01:28:38 GMT

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

Gary Gregory commented on LOG4J2-998:
-------------------------------------

FYI: I pushed snapshots of all the jars except {{log4j-perf}} to https://repository.apache.org/content/repositories/snapshots/

> Make org.apache.logging.log4j.core.Logger#updateConfiguration protected
> -----------------------------------------------------------------------
>
>                 Key: LOG4J2-998
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-998
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.1
>            Reporter: Mariano Gonzalez
>             Fix For: 2.3
>
>
> Hello,
> I'm using log4j2 as the foundation for a centralized logging infrastructure inside an
application container. For such requirement, I need to be able to override the org.apache.logging.log4j.core.Logger#updateConfiguration
method. However, that method has package visibility and thus cannot be gracefully overriden.
> It'd be great if that method could be protected so that subclasses can redefine it. 
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message