[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893952#action_12893952
]
Ralph Goers commented on LOG4J2-41:
-----------------------------------
I'm not suggesting that this issue be closed at this point, just that it
changes my perspective on the value of fixing it. There are distinct advantages
in using Enums over static ints. The other thing to consider is that every
level has a corresponding set of methods on the Logger interface. These won't
exist for custom levels unless a custom Logger interface is used. It would take
a bit of convincing for me to understand how this would be a good thing.
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
