This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch 2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/2.x by this push:
new fb8c1afb53 Fix Javadoc typo
fb8c1afb53 is described below
commit fb8c1afb531d8def1a50853da4cafcad2e1dc584
Author: Gary Gregory <[email protected]>
AuthorDate: Fri May 31 09:36:36 2024 -0400
Fix Javadoc typo
---
.../apache/logging/log4j/core/selector/ClassLoaderContextSelector.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/log4j-core/src/main/java/org/apache/logging/log4j/core/selector/ClassLoaderContextSelector.java
b/log4j-core/src/main/java/org/apache/logging/log4j/core/selector/ClassLoaderContextSelector.java
index 4af3e72d6a..0f2bc83f87 100644
---
a/log4j-core/src/main/java/org/apache/logging/log4j/core/selector/ClassLoaderContextSelector.java
+++
b/log4j-core/src/main/java/org/apache/logging/log4j/core/selector/ClassLoaderContextSelector.java
@@ -36,7 +36,7 @@ import org.apache.logging.log4j.util.StackLocatorUtil;
/**
* This ContextSelector chooses a LoggerContext based upon the ClassLoader of
the caller. This allows Loggers assigned
- * to static variables to be released along with the classes that own then.
Other ContextSelectors will generally cause
+ * to static variables to be released along with the classes that own them.
Other ContextSelectors will generally cause
* Loggers associated with classes loaded from different ClassLoaders to be
co-mingled. This is a problem if, for
* example, a web application is undeployed as some of the Loggers being
released may be associated with a Class in a
* parent ClassLoader, which will generally have negative consequences.
