[
https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886359#comment-13886359
]
Nick Williams commented on LOG4J2-522:
--------------------------------------
-0: Paul has suggested we hold off on "Using Custom Levels with a
Custom/Wrapper Interface" until a request actually comes in for it from the
community. I +1ed his suggestion. If we indeed decide to hold off on that,
there is _no_ reason to do this task yet. In fact, there's compelling reason
_not_ to do this task yet:
* If we decide to proceed with "Using Custom Levels with a Custom/Wrapper
Interface" at a later point—whether it's 2.0.x or 2.1, etc.—we _*CAN*_ split
these interfaces without affecting binary compatibility.
* However, if we split these interfaces now, we _*CANNOT*_ un-split them
without affecting binary compatibility.
> Split Logger interface in two with named level methods (info, warn, ...) in
> the subinterface.
> ---------------------------------------------------------------------------------------------
>
> Key: LOG4J2-522
> URL: https://issues.apache.org/jira/browse/LOG4J2-522
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.0-beta9
> Environment: Apache Maven 3.1.1
> (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400)
> Maven home: C:\Java\apache-maven-3.1.1\bin\..
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_51\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Attachments: log4j-522.diff
>
>
> Split Logger interface in two with named level methods (info, warn, ...) in
> the subinterface. This should help create custom loggers that are not tied to
> the stock Level "DSL".
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
