From dd9b43dc9c3e4913730b2745d5fb5b7007343d74 Mon Sep 17 00:00:00 2001 From: Glen Stampoultzis Date: Fri, 29 Mar 2002 11:08:24 +0000 Subject: [PATCH] Oops. Missed something. git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@352296 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/xdocs/hssf/how-to.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/documentation/xdocs/hssf/how-to.xml b/src/documentation/xdocs/hssf/how-to.xml index 01d59232d..d642f6152 100644 --- a/src/documentation/xdocs/hssf/how-to.xml +++ b/src/documentation/xdocs/hssf/how-to.xml @@ -446,7 +446,7 @@ down problems.

So Why use commons logging rather than log4j? Well the following discussion from the jakarta-general mailing list sums it up pretty well. (Thanks Morgan)

-

Here's the problem, as I see it. +

Here's the problem, as I see it.

Suppose Commons component A decides to adopt Log4J, Commons component B decides to adopt LogKit, and Commons component C adopts JDK1.4 logging.