logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikael Ståldal (JIRA) <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
Date Sun, 21 Aug 2016 08:51:20 GMT

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

Mikael Ståldal commented on LOG4J2-1528:

{{ConfigurationBuilder.newLogger(String, Level)}} and {{ConfigurationBuilder.newRootLogger(Level)}}
set includeLocation to true by default.

Is that how it should be? Is that consistent with configuration files?

Judging from {{LoggerConfig.includeLocation}} it seems like includeLocation on loggers is
a tri-state option where the absence is different from either true or false.

But this absence of includeLocation is not possible to express with ConfigurationBuilder currently.
Should it be?

> Serialize configuration into a log4j2.xml file
> ----------------------------------------------
>                 Key: LOG4J2-1528
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1528
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Configurators
>    Affects Versions: 2.6.2
>            Reporter: Mikael Ståldal
>            Assignee: Mikael Ståldal
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.

This message was sent by Atlassian JIRA

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

View raw message