This is an automated email from the ASF dual-hosted git repository.

rgoers pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 86abef00503a05639b01e22651d39dd05042065c
Author: Ralph Goers <[email protected]>
AuthorDate: Sun Aug 2 13:44:35 2020 -0700

    LOG4J2-2822 - Javadoc link in ThreadContext description was incorrect
---
 log4j-api/src/main/java/org/apache/logging/log4j/ThreadContext.java | 3 ++-
 src/changes/changes.xml                                             | 3 +++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git 
a/log4j-api/src/main/java/org/apache/logging/log4j/ThreadContext.java 
b/log4j-api/src/main/java/org/apache/logging/log4j/ThreadContext.java
index 18471b7..d643cd9 100644
--- a/log4j-api/src/main/java/org/apache/logging/log4j/ThreadContext.java
+++ b/log4j-api/src/main/java/org/apache/logging/log4j/ThreadContext.java
@@ -42,7 +42,8 @@ import org.apache.logging.log4j.util.PropertiesUtil;
  * The ThreadContext allows applications to store information either in a Map 
or a Stack.
  * <p>
  * <b><em>The MDC is managed on a per thread basis</em></b>. To enable 
automatic inheritance of <i>copies</i> of the MDC
- * to newly created threads, enable the {@value 
DefaultThreadContextMap#INHERITABLE_MAP} Log4j system property.
+ * to newly created threads, enable the {@value 
org.apache.logging.log4j.spi.DefaultThreadContextMap#INHERITABLE_MAP}
+ * Log4j system property.
  * </p>
  * @see <a 
href="https://logging.apache.org/log4j/2.x/manual/thread-context.html";>Thread 
Context Manual</a>
  */
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index eaad7af..5420541 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -30,6 +30,9 @@
          - "remove" - Removed
     -->
     <release version="2.14.0" date="2020-MM-DD" description="GA Release 
2.14.0">
+      <action issue="LOG4J2-2822" dev="rgoers" type="fix">
+        Javadoc link in ThreadContext description was incorrect.
+      </action>
       <action issue="LOG4J2-2894" dev="rgoers" type="fix">
         Fix spelling error in log message.
       </action>

Reply via email to