[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Commented] (LOG4J2-589) Use forName instead of getLevel and valueOf for configuration
From:       "Gary Gregory (JIRA)" <jira () apache ! org>
Date:       2014-03-31 13:10:15
Message-ID: JIRA.12705634.1396268030716.35958.1396271415005 () arcas
[Download RAW message or body]


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

Gary Gregory commented on LOG4J2-589:
-------------------------------------

Please feel free to provide a patch with unit tests :)

> Use forName instead of getLevel and valueOf for 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
> 
> 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
(v6.2#6252)

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


[prev in list] [next in list] [prev in thread] [next in thread]