logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme
Date Sun, 05 Feb 2017 21:48:42 GMT

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

Matt Sicker commented on LOG4J2-1431:

Thankfully, parsing the property names turned out to be a lot simpler than initially expected
thanks to some regular expressions. This feature is pretty much code complete in the LOG4J2-1431
branch. I'd still like to update the manual to reference the normalized property names instead
of the mish-mash we have currently. Here are some random examples of updates:

* log4j2.AsyncQueueFullPolicy -> log4j2.asyncQueueFullPolicy
* log4j.configurationFile -> log4j2.configurationFile
* AsyncLogger.ExceptionHandler -> log4j2.asyncLoggerExceptionHandler
* Log4jContextSelector -> log4j2.contextSelector

> Simplify log4j system property naming scheme
> --------------------------------------------
>                 Key: LOG4J2-1431
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1431
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
> As I wonder how to prefix yet another configurable system property, I noticed we have
five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> <no prefix>
> What I'd like to do is strip out all those prefixes and allow any of them, but change
the documentation to use only a single consistent prefix. This would also make it simpler
when writing the properties into a log4j2.component.properties file as you could omit all
the prefixes as they won't clash with other libraries.

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