[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443428#comment-15443428
]
Remko Popma commented on LOG4J2-1010:
-------------------------------------
Thanks for the tip. I find that links in the text tend to pull the user's eye
and come to dominate the paragraph. Sometimes this is useful for emphasis,
sometimes this distracts from the main point.
What I tend to do is use \{@code ...\} to mark class and method names, and then
refer to them in @see tags at the bottom of the class description. In the
javadoc for methods, return types and parameter types already have links, so I
only use \{@link ...\} for other objects and methods.
> Injectable context properties
> -----------------------------
>
> Key: LOG4J2-1010
> URL: https://issues.apache.org/jira/browse/LOG4J2-1010
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.2
> Reporter: Mikael Ståldal
> Assignee: Remko Popma
> Fix For: 2.7
>
> Attachments: properties.patch
>
>
> It would be useful to have a way to inject context properties into a
> {{LogEvent}}, as an alternative to {{ThreadContext}}.
> In an asynchronous environment, using ThreadContext as currently implemented
> is not so useful since JVM threads might not be coupled to the logical flow
> of the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
