* Even when using an AccessController, however, this method can still - * throw SecurityException. Commons-logging basically relies on the + * throw SecurityException. Commons Logging basically relies on the * ability to access classloaders. A policy that forbids all * classloader access will also prevent commons-logging from working: * currently this method will throw an exception preventing the entire app diff --git a/src/main/java/org/apache/commons/logging/package-info.java b/src/main/java/org/apache/commons/logging/package-info.java index f6cd5dd..727f767 100644 --- a/src/main/java/org/apache/commons/logging/package-info.java +++ b/src/main/java/org/apache/commons/logging/package-info.java @@ -147,7 +147,7 @@ *
The basic principle is that the user is totally responsible for the * configuration of the underlying logging system. - * Commons-logging should not change the existing configuration.
+ * Commons Logging should not change the existing configuration. *Each individual Log implementation may * support its own configuration properties. These will be documented in the * class descriptions for the corresponding implementation class.
diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml index 4736127..e3fd5db 100644 --- a/src/site/xdoc/index.xml +++ b/src/site/xdoc/index.xml @@ -36,7 +36,7 @@ of a particular one on the overall application that the library is a part of.The Logging package is an ultra-thin bridge between different logging implementations. A library that uses the commons-logging API can be used with -any logging implementation at runtime. Commons-logging comes with support for a +any logging implementation at runtime. Commons Logging comes with support for a number of popular logging implementations, and writing adapters for others is a reasonably simple task.