[
https://issues.apache.org/jira/browse/LOG4J2-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317381#comment-16317381
]
Remko Popma commented on LOG4J2-2177:
-------------------------------------
About log4j-api: I agree our current situation is confusing: Some classes in
log4j-api's {{org.apache.logging.log4j.util}} package are API, and some are
purely intended for internal use. This is unfortunate.
We should take a good look at which is which and document this somehow (unless
we think that moving packages for the classes we consider "internal" is an
option - but this would break binary compatibility).
We could have an {{@Internal}} annotation (like [poi
did|https://poi.apache.org/apidocs/org/apache/poi/util/Internal.html]), and/or
clarify in the Javadoc of each class as well as the package javadoc.
Unfortunately Java 9 modules only allow exporting at the package level, not at
the class level, so this won't help us.)
> Replace use of deprecated Core API
> org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String,
> String>)
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2177
> URL: https://issues.apache.org/jira/browse/LOG4J2-2177
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.10.0
> Reporter: Gary Gregory
> Assignee: Gary Gregory
>
> Replace use of deprecated Core API
> {{org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map<String,
> String>)}}
> In order to implement this cleanly, the internal class
> {{org.apache.logging.log4j.core.impl.ContextDataFactory}} will change its API
> return values from {{StringMap}} to {{IndexedStringMap}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
