commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From skitch...@apache.org
Subject svn commit: r178063 - /jakarta/commons/proper/logging/branches/simon-1.1/README.txt
Date Tue, 24 May 2005 02:43:21 GMT
Author: skitching
Date: Mon May 23 19:43:20 2005
New Revision: 178063

URL: http://svn.apache.org/viewcvs?rev=178063&view=rev
Log:
General updates.

Modified:
    jakarta/commons/proper/logging/branches/simon-1.1/README.txt

Modified: jakarta/commons/proper/logging/branches/simon-1.1/README.txt
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/simon-1.1/README.txt?rev=178063&r1=178062&r2=178063&view=diff
==============================================================================
--- jakarta/commons/proper/logging/branches/simon-1.1/README.txt (original)
+++ jakarta/commons/proper/logging/branches/simon-1.1/README.txt Mon May 23 19:43:20 2005
@@ -1,27 +1,31 @@
 The code here is an experiment based very heavily upon ideas from SLF4J/UGLI but 
 including the best of JCL too.
 
-The code is currently fairly rough around the edges. Complaints about minor 
-issues are not likely to be received with enthusiasm!
+The code is currently fairly rough around the edges. Comments about fundamental
+architectural issues are very welcome. Complaints about minor issues like
+error-checking or spelling are not likely to be received with enthusiasm!
 
 The LogFactory and Log classes should be compatible with 99.99% of existing
 code that uses JCL. Code that *implements* adapters for libraries are simply
 not compatible - but that's not likely to be a major issue.
 
-Run "ant jcl-app" to generate the following jars in target:
-  * jcl-spi.jar
-  * jcl-NoOp.jar
-  * jcl-Simple.jar
-  * jcl-Jdk14.jar
-  * jcl-Log4J12.jar
+Run "ant jcl-all" to generate the following jars in target:
+  * commons-logging-core.jar
+  * commons-logging-test.jar
+  * commons-logging-nop.jar
+  * commons-logging-simple.jar
+  * commons-logging-jdk14.jar
+  * commons-logging-log4j12.jar
 
-Ordinary applications just deploy jcl-spi.jar AND the appropriate
+Run "ant test" to execute the (currently very rough) unit tests.
+
+Ordinary applications just deploy commons-logging-core.jar AND the appropriate
 jar for whatever library they want to bind to.
 
 In webserver environments:
- * deploy jcl-spi *only once*, via a classloader that is not lower
-   than a jcl-XXXX adapter jar is deployed. 
- * deploy jcl-XXXX adapter jars as often as desired.
+ * deploy commons-logging-core *only once*, via a classloader that is not lower
+   than a commons-logging-xxxx adapter jar is deployed. 
+ * deploy commons-logging-xxxx adapter jars as often as desired.
  * if you want code in non-leaf classloaders which use JCL to try
    to log via loglibs in context classloaders, then set system
    property "org.apache.commons.logging.context=true". Without
@@ -34,9 +38,9 @@
 be coming soon..
 
 Benefits:
- * no auto-detection of logging libs; you deploy jcl-xxx.jar, you
+ * no auto-detection of logging libs; you deploy commons-logging-xxx.jar, you
    get logging via xxx. Well, unless you've enabled the "context"
-   feature in which case it might go to whatever jcl-yyy.jar is
+   feature in which case it might go to whatever commons-logging-yyy.jar is
    deployed in the context classloader.
  * very simple
  * very fast



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


Mime
View raw message