You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by ce...@apache.org on 2001/01/18 08:49:41 UTC
cvs commit: jakarta-log4j/xdocs index.xml
ceki 01/01/17 23:49:41
Modified: . TODO build.inc manifest.mf
doc FAQ.html HISTORY manual.html
org/apache/log4j/xml DOMConfigurator.java
org/apache/log4j/xml/test DOMTest.java
xdocs index.xml
Log:
Started work on log4j 1.1.
Revision Changes Path
1.4 +5 -2 jakarta-log4j/TODO
Index: TODO
===================================================================
RCS file: /home/cvs/jakarta-log4j/TODO,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- TODO 2001/01/05 21:08:51 1.3
+++ TODO 2001/01/18 07:49:36 1.4
@@ -1,13 +1,15 @@
TODO
+- Clean up the association of renderers and hierarchies
+- log4j: namespace in DTD
+- Allow the message object to be seen by Appenders and Layouts.
- Mapped Diagnostic Contexts
- FailOverAppender
-- Complete multiple hierachy support, give an a Sink example
+
- Graceful congiguration merging
- Integrate tons of GUI code.
- JDBCAppender.
-- SAX configurator?
- Time based rolling.
- SSL logging.
- Authenticated logging.
@@ -21,6 +23,7 @@
DONE
+- Complete multiple hierachy support.
- JMSAppender.
- SMTPAppender.
- Automatic configuration file reloading.
1.12 +1 -1 jakarta-log4j/build.inc
Index: build.inc
===================================================================
RCS file: /home/cvs/jakarta-log4j/build.inc,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- build.inc 2001/01/11 23:29:14 1.11
+++ build.inc 2001/01/18 07:49:36 1.12
@@ -75,7 +75,7 @@
<property name="classes" value="classes" />
<property name="stem" value="org/apache/log4j" />
<property name="build.compiler" value="jikes"/>
- <property name="version" value="1.0.4"/>
+ <property name="version" value="1.1"/>
</target>
1.5 +1 -1 jakarta-log4j/manifest.mf
Index: manifest.mf
===================================================================
RCS file: /home/cvs/jakarta-log4j/manifest.mf,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- manifest.mf 2001/01/11 23:29:14 1.4
+++ manifest.mf 2001/01/18 07:49:37 1.5
@@ -2,7 +2,7 @@
Name: org/apache/log4j/
Implementation-Title: log4j
-Implementation-Version: 1.0.4
+Implementation-Version: 1.0.5
Implementation-Vendor: "Apache Softwate Foundation"
1.2 +3 -13 jakarta-log4j/doc/FAQ.html
Index: FAQ.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/doc/FAQ.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FAQ.html 2001/01/11 11:59:31 1.1
+++ FAQ.html 2001/01/18 07:49:37 1.2
@@ -146,20 +146,10 @@
There are many other logging packages out there. I know of <a
href=http://www.homestead.com/JavaLog/>Grace Software's JavaLog</a>,
+<a href=http://www.alphaworks.ibm.com/tech/loggingtoolkit4j>JLog</a>,
<a href=http://www.sw-zoo.org/>Software ZOO's toolkit</a>, <a
-href=http://www.eli.sdsu.edu/java-SDSU/>SDSU logging package</a> and
-many others.
-
-<p>Many users confuse <a
-href=http://www.alphaworks.ibm.com/tech/loggingtoolkit4j>JLog</a> with
-log4j. The two packages originated at different parts of IBM. JLog was
-developed at IBM Tivoli whereas log4j was independently developed at
-the IBM Research Laboratory. Both packages are listed on IBM's
-alphaWorks, although, as of April 2000, log4j moved to <a
-href="http://www.log4j.org">greener pastures</a>.
-
-<p>Please note that log4j is not an IBM controlled nor IBM sponsored
-project.
+href=http://www.eli.sdsu.edu/java-SDSU/>SDSU logging package</a>. This
+list is not exhaustive.
<a name=usageExample><h4>Is there example code for using log4j?</h4>
1.6 +21 -0 jakarta-log4j/doc/HISTORY
Index: HISTORY
===================================================================
RCS file: /home/cvs/jakarta-log4j/doc/HISTORY,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- HISTORY 2001/01/11 23:29:15 1.5
+++ HISTORY 2001/01/18 07:49:39 1.6
@@ -5,6 +5,23 @@
client code.
[***] Changes requiring important modifications to existing client code.
+
+ February ??, 2001
+
+ - Release of version 1.1 (the 21st major release)
+
+ - Changed the name of the configuration element to log4j:configuration in the
+ log4j.dtd. All configuration files written in XML need to be
+ modified. [**]
+
+ The following perl command can help:
+
+ > perl -p -i.bak -e "s/configuration/log4j:configuration/;" file1.xml .. fileN.xml
+
+
+ - Fixed the errouneously thrown IOInterruptedException when the AsyncAppender
+ was closed. [*]
+
January 12th, 2001
- Release of version 1.0.4 (the 20th major release)
@@ -57,6 +74,10 @@
- Release of version 1.0 (the 20th major release)
- Package hierarchy now starts at org.apache.log4j. [***]
+
+ The following perl command can help in the transition:
+
+ > perl -p -i.bak -e "s/org.log4j/org.apache.log4j/;" file1.java .. fileN.java
- Added the fatal() family of methods to the Category
class. Moreoever, the EMERG priority has been removed from the
1.6 +2 -2 jakarta-log4j/doc/manual.html
Index: manual.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/doc/manual.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- manual.html 2001/01/10 22:52:21 1.5
+++ manual.html 2001/01/18 07:49:39 1.6
@@ -66,8 +66,8 @@
development cycle, a sufficiently rich logging package could also be
viewed as an auditing tool.
-<p>As Brian W. Kernigan and Rob Pike put it in their excellent book
-<i>"The Practice of Programming"</i>
+<p>As Brian W. Kernigan and Rob Pike put it in their truely excellent
+book <i>"The Practice of Programming"</i>
<pre>
As personal choice, we tend not to use debuggers beyond getting a
stack trace or the value of a variable or two. One reason is that it
1.9 +5 -2 jakarta-log4j/org/apache/log4j/xml/DOMConfigurator.java
Index: DOMConfigurator.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/org/apache/log4j/xml/DOMConfigurator.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- DOMConfigurator.java 2001/01/17 14:26:58 1.8
+++ DOMConfigurator.java 2001/01/18 07:49:40 1.9
@@ -304,8 +304,11 @@
// to protect potential log operations while category
// configuration is in progress.
synchronized(cat) {
- cat.setAdditivity(OptionConverter.toBoolean(
- categoryElement.getAttribute(ADDITIVITY_ATTR), true));
+ boolean additivity = OptionConverter.toBoolean(
+ categoryElement.getAttribute(ADDITIVITY_ATTR), true);
+
+ LogLog.debug("Setting ["+cat.getName()+"] additivity to ["+additivity+"].");
+ cat.setAdditivity(additivity);
parseChildrenOfCategoryElement(categoryElement, cat, false);
}
}
1.4 +2 -0 jakarta-log4j/org/apache/log4j/xml/test/DOMTest.java
Index: DOMTest.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/org/apache/log4j/xml/test/DOMTest.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- DOMTest.java 2000/12/19 13:14:06 1.3
+++ DOMTest.java 2001/01/18 07:49:40 1.4
@@ -86,5 +86,7 @@
cat.error("Message " + ++i, e);
root.error("Message " + i, e);
+
+ Category.shutdown();
}
}
1.2 +1 -1 jakarta-log4j/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/xdocs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 2001/01/10 18:33:10 1.1
+++ index.xml 2001/01/18 07:49:40 1.2
@@ -51,7 +51,7 @@
not. Actual logging is also quite fast, ranging from 79 micro-seconds
using the SimpleLayout, 164 micro-seconds using the TTCCLayout and
around a millisecond when printing exceptions. The performance of the
-PatternLayout is almost as good as the dedicated patterns, except that
+PatternLayout is almost as good as the dedicated layouts, except that
it is a lot more flexible.</p>
<p>The package is being constantly improved thanks to input from users