svn commit: r395344 - /jakarta/commons/proper/logging/trunk/xdocs/guide.xml

[rd...@apache.org]

Author: rdonkin
Date: Wed Apr 19 11:35:15 2006
New Revision: 395344

URL: http://svn.apache.org/viewcvs?rev=395344&view=rev
Log:
Added a little explaination concerning the recommendation.

Modified:
    jakarta/commons/proper/logging/trunk/xdocs/guide.xml

Modified: jakarta/commons/proper/logging/trunk/xdocs/guide.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/guide.xml?rev=395344&r1=395343&r2=395344&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/xdocs/guide.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/guide.xml Wed Apr 19 11:35:15 2006
@@ -113,9 +113,12 @@
 In most cases, including the (full) <code>commons-logging.jar</code> in the classpath
 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
-need to do any configuration at all! Note, however, that providing a simple
-commons-logging.properties file which specifies the concrete logging library to be
-used is recommended, as it saves any possible confusion.
+need to do any configuration at all! 
+		</p><p>
+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>
         <subsection name='Configuration'>
             <p>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org