You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Philipp Knobel (JIRA)" <ji...@apache.org> on 2016/07/05 15:40:10 UTC

[jira] [Created] (LOG4J2-1455) CompositeConfiguration Logger level not overridable

Philipp Knobel created LOG4J2-1455:
--------------------------------------

             Summary: CompositeConfiguration Logger level not overridable
                 Key: LOG4J2-1455
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1455
             Project: Log4j 2
          Issue Type: Bug
          Components: Configurators
    Affects Versions: 2.6
            Reporter: Philipp Knobel


Trying to have a logger level overriden within compositeConfiguration, seems to be not working, see https://github.com/philnate/logging-log4j2/commit/e743e7c05fd282b0f75b285fe41ca18282403a2a

It looks like that if there's already a logger we forget to copy over it's attribute, like we do if the targetNode doesn't exist.



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