[
https://issues.apache.org/jira/browse/LOG4J2-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883655#comment-13883655
]
Matt Sicker commented on LOG4J2-33:
-----------------------------------
No, you're perfectly correct. I'm not sure how to go about getting that data
otherwise. This particular style might not be feasible. I'm working on an
example using aspects for logging field access and method/constructor calls, so
that might be more promising or useful. The thing is, though, we can't just add
AOP as a dependency for log4j-api, so I'm not sure where the best place to put
it would be. Perhaps a module/bundle?
> Support Annotations
> -------------------
>
> Key: LOG4J2-33
> URL: https://issues.apache.org/jira/browse/LOG4J2-33
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Reporter: Ralph Goers
> Fix For: 0.1
>
> 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
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
