Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Spelling and version 1.3.0

Browse Source
This commit is contained in:
Gary Gregory
2023-11-26 13:51:14 -05:00
parent 4b13fdaf94
commit e8a558b708
14 changed files with 31 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/site/xdoc/index.xml
View File

@@ -108,10 +108,10 @@ Binary and source distributions are available
have been encountered when using commons-logging in servlet containers or j2ee
containers where complex classpaths are present and multiple copies of
commons-logging libraries are present at different levels.</p>
<p>This release also adds support for the TRACE level added to log4j in the
<p>This release also adds support for the TRACE level added to Log4j in the
1.2.12 release. In former commons-logging versions, the log.trace method
caused log4j to output the message at the DEBUG level (the lowest level
supported by log4j at that time).</p>
caused Log4j to output the message at the DEBUG level (the lowest level
supported by Log4j at that time).</p>
<p>For the full details, see the release notes for this version.</p>
</subsection>
<subsection name='1.0.5 Release (Alpha)'>

2
src/site/xdoc/proposal.xml
View File

@@ -53,7 +53,7 @@ implementations.
The package should :
<ul>
<li>Have an API which should be as simple to use as possible</li>
<li>Provide support for log4j</li>
<li>Provide support for Log4j</li>
<li>Provide pluggable support for other logging APIs</li>
</ul>
</p>

4
src/site/xdoc/troubleshooting.xml
View File

@@ -426,7 +426,7 @@ implementation.
Because the commons-logging-api.jar in the container does not contain any
log-library-adapter classes, updated behavior for these <i>will</i> be
seen when logging 1.1 is bundled in WEB-INF/lib. In particular, the
support for log4j's TRACE level will take effect without having to update
support for Log4j's TRACE level will take effect without having to update
the container.
</p>
<p>
@@ -437,7 +437,7 @@ implementation.
can only see their matching concrete logging library if that library is
available in the same classpath. Bundling the full commons-logging jarfile
(with adapters) into the system classpath therefore means that logging
libraries (eg log4j) within WEB-INF/lib are not accessible.
libraries (eg Log4j) within WEB-INF/lib are not accessible.
</p>
<p>
Note that the behavior described here only applies if the standard Tomcat