logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-589) Allow the use of custom levels in configuration
Date Wed, 24 Sep 2014 02:37:34 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Remko Popma updated LOG4J2-589:
    Fix Version/s:     (was: 2.1)

This proposal is the missing piece that will make custom levels just as powerful as built-in
levels. The [code generator|http://logging.apache.org/log4j/2.x/manual/customloglevels.html#CodeGen]
addressed ease-of-use in the application code, this will address configuration.

Before starting on an implementation I would like feedback on the idea and on the configuration
syntax (see comment above).


> Allow the use of custom levels in configuration
> -----------------------------------------------
>                 Key: LOG4J2-589
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-589
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Configurators
>    Affects Versions: 2.0-rc1
>            Reporter: James Hutton
>              Labels: configuration, custom, level
>             Fix For: 2.2
> Previous title: Use forName instead of getLevel and valueOf for configuration
> Without this one cannot use custom log levels in configuration without forking a large
amount of code.  Either the forName method needs to be removed and custom log levels should
be explicitly forbidden, or support should be consistent.
> Classes that would need to be modified:
> BaseConfiguration, NullConfiguration, and DefaultConfiguration.

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