[
https://issues.apache.org/jira/browse/LOG4J2-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149306#comment-14149306
]
Remko Popma commented on LOG4J2-589:
------------------------------------
Thanks for your feedback! I pushed an update on the LOG4J2-589 branch that
incorporates your suggestions.
CustomLevel elements now must be configured in a containing CustomLevels
element.
* Renamed CustomLevelPlugin to CustomLevelConfig
* Added method Configuration#getCustomLevels - returns List<CustomLevelConfig>
* Added plugin CustomLevels to act as the CustomLevel container
* Updated manual page
* Updated schema
Please take a look.
If no objections I'll merge this into master tomorrow afternoon JST (late
Friday night EDT).
> Allow filtering on 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
> Assignee: Remko Popma
> Labels: configuration, custom, level
> Fix For: 2.1
>
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
