logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-33) Support Annotations
Date Sun, 23 Mar 2014 22:19:45 GMT

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

Ralph Goers commented on LOG4J2-33:

The reason I've never done anything with this issue is that I am not sure I really see the
value in doing



@Log Logger logger;


Logger logger = LogManager.getLogger(this.getClass());

except that the latter allows you to specify a different logger name.

I like the idea of @LogEntryExit as that really does save some coding, especially if you can
add it to the class and have it apply to all methods. 

> Support Annotations
> -------------------
>                 Key: LOG4J2-33
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-33
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API
>    Affects Versions: 2.0-rc2
>            Reporter: Ralph Goers
>             Fix For: 0.1, 2.0-rc2
>         Attachments: 0001-Add-Loggable.patch
> The Log4j API should support using annotations as provided in Java 6 so applications
can use them instead of calls to logger APIs. This is especially useful for entering &
exiting type of events, but could be used wherever annotations are allowed.

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