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

Added a little explaination concerning the recommendation.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@395344 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Robert Burrell Donkin
2006-04-19 18:35:15 +00:00
parent 7caedf2e1d
commit 5342620a9f
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
xdocs/guide.xml
View File

@@ -113,9 +113,12 @@ As far as possible, JCL tries to be as unobtrusive as possible.
In most cases, including the (full) <code>commons-logging.jar</code> in the classpath In most cases, including the (full) <code>commons-logging.jar</code> in the classpath
should result in JCL configuring itself in a reasonable manner. should result in JCL configuring itself in a reasonable manner.
There's a good chance that it'll guess your preferred logging system and you won't There's a good chance that it'll guess your preferred logging system and you won't
need to do any configuration at all! Note, however, that providing a simple need to do any configuration at all!
commons-logging.properties file which specifies the concrete logging library to be </p><p>
used is recommended, as it saves any possible confusion. Note, however, that if you have a particular preference then providing a simple
<code>commons-logging.properties</code> file which specifies the concrete logging library to be
used is recommended, since (in this case) JCL will log only to that system
and will report any configuration problems that prevent that system being used.
</p> </p>
<subsection name='Configuration'> <subsection name='Configuration'>
<p> <p>