logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel Grandin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-41) Extensible Log Level
Date Tue, 26 Nov 2013 06:45:36 GMT

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

Noel Grandin commented on LOG4J2-41:

I don't see this issue "keep coming up". 
Generally about once a year and mostly people are pointed in the direction of a reasonable
solution that works with the existing API.

I'll repeat my comment from earlier on the mailing list:
Every extension to an API adds complexity and cost
(a) that extension is used by a vanishingly small fraction of the userbase
(b) there are other mechanisms that can accomplish the given ends (e.g. Markers)
(c) the cost of the extension will be borne by every plugin author
then the cost of the extension is very dubious.

> Extensible Log Level
> --------------------
>                 Key: LOG4J2-41
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-41
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>            Reporter: Ralph Goers
> It is desirable to have the Level be an enum. However, it is also desirable to let users
add new log levels. These goals are in opposition to each other since enum classes are final.
In addition, adding new levels implies adding new methods to the Logger interface (or some
counterpart to it). This would be unworkable.

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