From 5342620a9fbeed63cc524a6cb01efdbf15c1c41a Mon Sep 17 00:00:00 2001 From: Robert Burrell Donkin Date: Wed, 19 Apr 2006 18:35:15 +0000 Subject: [PATCH] Added a little explaination concerning the recommendation. git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@395344 13f79535-47bb-0310-9956-ffa450edef68 --- xdocs/guide.xml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/xdocs/guide.xml b/xdocs/guide.xml index aaf5805..0d847ad 100644 --- a/xdocs/guide.xml +++ b/xdocs/guide.xml @@ -113,9 +113,12 @@ As far as possible, JCL tries to be as unobtrusive as possible. In most cases, including the (full) commons-logging.jar 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! +

+Note, however, that if you have a particular preference then providing a simple +commons-logging.properties 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.