You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by ce...@apache.org on 2005/04/29 19:39:41 UTC
cvs commit: logging-log4j/src/xdocs/stylesheets project.xml
ceki 2005/04/29 10:39:41
Modified: . Tag: v1_2-branch build.xml
docs Tag: v1_2-branch FAQ.html
src/xdocs download.xml history.xml
src/xdocs/stylesheets project.xml
Log:
Minor chages. Preparing for 1.2.10
PR:
Obtained from:
Submitted by:
Reviewed by:
Revision Changes Path
No revision
No revision
1.34.2.15 +2 -1 logging-log4j/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/logging-log4j/build.xml,v
retrieving revision 1.34.2.14
retrieving revision 1.34.2.15
diff -u -r1.34.2.14 -r1.34.2.15
--- build.xml 28 Apr 2005 20:36:23 -0000 1.34.2.14
+++ build.xml 29 Apr 2005 17:39:41 -0000 1.34.2.15
@@ -270,7 +270,7 @@
<javac deprecation="${deprecation}"
srcdir="${java.source.dir}"
destdir="${javac.dest}"
- includes="${stem}/net/JMS*.java">
+ includes="${stem}/net/JMS*.java, ${stem}/or/jms/*.java">
<classpath refid="compile.classpath"/>
</javac>
</target>
@@ -411,6 +411,7 @@
<link href="http://java.sun.com/products/jdk/1.3/docs/api/"/>
<link href="http://java.sun.com/j2ee/sdk_1.3/techdocs/api/"/>
+ <link href="http://www.slf4j.org/api/"/>
<classpath refid="compile.classpath"/>
</javadoc>
</target>
No revision
No revision
1.15.2.4 +61 -27 logging-log4j/docs/Attic/FAQ.html
Index: FAQ.html
===================================================================
RCS file: /home/cvs/logging-log4j/docs/Attic/FAQ.html,v
retrieving revision 1.15.2.3
retrieving revision 1.15.2.4
diff -u -r1.15.2.3 -r1.15.2.4
--- FAQ.html 29 Apr 2005 17:07:43 -0000 1.15.2.3
+++ FAQ.html 29 Apr 2005 17:39:41 -0000 1.15.2.4
@@ -83,7 +83,8 @@
</table>
<table class="index-question">
<td nowrap="true" valign="top">Question 1.6</td>
- <td><a href="#1.6">What documentation should I read to learn log4j?</a></td>
+ <td><a href="#1.6">What documentation should I read to learn more about
+ log4j?</a></td>
</table>
<table class="index-question">
<td nowrap="true" valign="top">Question 1.7</td>
@@ -93,6 +94,11 @@
<td nowrap="true" valign="top">Question 1.8</td>
<td><a href="#1.8">What does log output look like?</a></td>
</table>
+ <table class="index-question">
+ <td nowrap="true" valign="top">Question 1.9</td>
+ <td><a href="#1.9">Why should I use log4j when JDK 1.4 already ships with a
+ logging API?</a></td>
+ </table>
<br/>
<div class="index-faqSection">
Section 2. <a href="#2"> Using log4j</a>
@@ -317,7 +323,10 @@
<li><p>log4j is based on a named logger hierarchy.</p></li>
- <li><p>log4j is fail-stop but not reliable.</p></li>
+ <li><p>log4j is fail-stop. However, altough it certainly
+ strives to ensure delivery, log4j does not guarantee that
+ each log statement will be delivered to its destination.
+ </p></li>
<li><p>log4j is thread-safe.</p></li>
@@ -337,17 +346,16 @@
remote Unix Syslog daemon, to a remote listener using JMS,
to the NT EventLog or even send e-mail. </p></li>
- <li><p>log4j uses 5 levels, namely DEBUG, INFO, WARN, ERROR and
- FATAL.
- </p></li>
+ <li><p>log4j uses 6 levels, namely TRACE, DEBUG, INFO, WARN,
+ ERROR and FATAL. </p></li>
<li><p>The format of the log output can be easily changed by
- extending the Layout class.
- </p></li>
+ extending the <code>Layout</code>
+ class. </p></li>
<li><p>The target of the log output as well as the writing
- strategy can be altered by implementations of the Appender
- interface. </p></li>
+ strategy can be altered by implementations of the
+ <code>Appender</code> interface. </p></li>
<li><p>log4j supports multiple output appenders per logger.
</p></li>
@@ -362,13 +370,14 @@
<p>See the <code>examples/</code> directory.</p>
<div class="question">
- <a name="1.6">1.6 What documentation should I read to learn log4j?</a>
+ <a name="1.6">1.6 What documentation should I read to learn more about
+ log4j?</a>
</div>
<p>Make sure to read the <a href="manual.html">short
- manual</a>. It is also recommended to you read <a href="https://www.qos.ch/shop/products/clm_t.jsp">The complete
- log4j manual</a>. Both documents were written by Ceki
- G�lc�.
+ manual</a>. It is also recommended to you read <a href="https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp">The complete
+ log4j manual</a> which is much more detailed and up to
+ date. Both documents were written by Ceki G�lc�.
</p>
<div class="question">
@@ -419,6 +428,26 @@
is the message of the statement.
</p>
+ <div class="question">
+ <a name="1.9">1.9 Why should I use log4j when JDK 1.4 already ships with a
+ logging API?</a>
+ </div>
+
+ <p>
+ Although both APIs are conceptually similar, the log4j API is
+ significantly more flexible and offers many more features, too
+ numerous to be listed here. You will discover that the
+ additional features and flexibility turn out to be
+ indispensable in the context of a mission-critical
+ application.
+ </p>
+
+ <p>The open and collaborative way in which log4j is developped
+ ensures that it continues to preserve and even widen its
+ competitive edge. At some point, input from bright developpers
+ from all over the world is bound to make a difference.
+ </p>
+
<div class="faqSection">
<a name="2">Section 2.</a> Using log4j
</div>
@@ -507,9 +536,9 @@
</p>
<h3>Better alternative based on message patterns</h3>
- <p>As of log4j version 1.3, there is a significantly more
+ <p>As of log4j version 1.3, there exists a significantly more
convenient alternative based on message patterns. Assuming
- <code>entry</code> is a non-primitive object, you can write:
+ <code>entry</code> is an object, you can write:
</p>
<p class="source">
@@ -517,14 +546,17 @@
</p>
<p>After evaluting whether to log or not, and only if the
- decision is affirmative, the logger instace will format the
- message and replace the '{}' pair with the string value of the
- <code>entry</code> parameter within the message pattern.
+ decision is positive, will the logger instace format the
+ message and replace the '{}' pair with the string value of
+ <code>entry</code>. In other words, the paramerized form does
+ not incur the cost of parameter construction in case the log
+ statement is disabled.
</p>
- <p>Thus, the following two lines will yield the exact sane
+ <p>Thus, the following two lines will yield the exact same
output. However, the second form will perform at least 30
- times faster in case the logger is disabled for DEBUG.
+ (thirty) times faster in case of a <em>disabled</em> logging
+ statement.
</p>
<p class="source">
@@ -532,8 +564,8 @@
l.debug("The new entry is {}.", entry);
</p>
- <p>A 2 argument variant is also availalble. Thus, you can also
- write:
+ <p>A two argument variant is also availalble. For example, you
+ can write:
</p>
<p class="source">
l.debug("The new entry is {}. It replaces {}.", entry, oldEntry);
@@ -1071,16 +1103,18 @@
</div>
<div class="menu_item"> <a href="./contributors.html">Contributors</a>
</div>
+ <div class="menu_item"> <a href="./chainsaw.html">Chainsaw</a>
+ </div>
<div class="menu_item"> <a href="./history.html">History</a>
</div>
- <div class="menu_header">Logging Services</div>
- <div class="menu_item"> <a href="http://logging.apache.org/">Home page</a>
+ <div class="menu_header">Support</div>
+ <div class="menu_item"> <a href="http://logging.apache.org/site/binindex.cgi">Binary distributions</a>
</div>
- <div class="menu_item"> <a href="http://logging.apache.org/site/news.html">News</a>
+ <div class="menu_item"> <a href="http://logging.apache.org/site/cvs-repositories.html">CVS Repositories</a>
</div>
- <div class="menu_item"> <a href="http://logging.apache.org/site/mission-statement.html">Mission</a>
+ <div class="menu_item"> <a href="http://logging.apache.org/site/mailing-lists.html">Mailing Lists</a>
</div>
- <div class="menu_item"> <a href="http://logging.apache.org/site/bylaws.html">Guidelines</a>
+ <div class="menu_item"> <a href="http://logging.apache.org/site/bugreport.html">Bug Reporting</a>
</div>
<div class="menu_header">Related Projects</div>
<div class="menu_item"> <a href="http://www.slf4j.org">SLF4J</a>
1.81 +9 -17 logging-log4j/src/xdocs/download.xml
Index: download.xml
===================================================================
RCS file: /home/cvs/logging-log4j/src/xdocs/download.xml,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- download.xml 20 Jan 2005 15:07:24 -0000 1.80
+++ download.xml 29 Apr 2005 17:39:41 -0000 1.81
@@ -8,7 +8,7 @@
<body>
- <section name="log4j version 1.2.9">
+ <section name="log4j version 1.2.10">
<p>Log4j is <a
href="http://logging.apache.org/site/binindex.cgi"><b>available
for download</b></a> from a number of mirrors. Please
@@ -16,9 +16,11 @@
bandwidth.
</p>
- <p>Log4j version 1.2.9, is identical to version 1.2.8,
- except that several key methods have been deprecated in
- preparation for version 1.3.0, the next major release of
+ <p>Log4j version 1.2.10 adds support for <a
+ href="http://www.slf4j.org">SLF4J</a>. It also fixes several
+ relatively minor bugs. Version 1.2.9 is identical to version
+ 1.2.8, except that several key methods have been deprecated
+ in preparation for version 1.3.0, the next major release of
log4j. These changes are intended to enforce the rule that
client code should never refer to the <code>Category</code>
class directly, but use the <code>Logger</code> class
@@ -35,21 +37,11 @@
<h2>log4j version 1.3 (alpha)</h2>
<p>An alpha version of log4j version 1.3 has been recently
- made available. It can be downloaded from the same As the
- alpha prefix indicates, this release is still being tested,
- future versions may bring further radical changes, and all
- the usual caveats apply.
+ made available. As the alpha prefix indicates, this release
+ is still being tested, future versions may bring further
+ radical changes, and all the usual caveats apply.
</p>
- <subsection name='Earlier Releases'>
- <p>We also maintain <a
- href="earlier.html">earlier
- versions of log4j</a> for download, intended for the
- curious paleontologist -- there seems to be quite a few
- of them!
- </p>
- </subsection>
-
</section>
1.14 +4 -3 logging-log4j/src/xdocs/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/logging-log4j/src/xdocs/history.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- history.xml 24 Nov 2004 19:35:19 -0000 1.13
+++ history.xml 29 Apr 2005 17:39:41 -0000 1.14
@@ -10,10 +10,11 @@
<section name="Project history">
+
<p>The <a href="HISTORY.txt"><b>project history</b></a> gives a
- brief summary of changes and additions. Users frequently
- report bugs that are solved in newer versions of log4j. Please
- have a look at the history file before asking for help.
+ brief summary of changes and additions. Users frequently report
+ bugs that are solved in newer versions of log4j. Please have a
+ look at the history file before asking for help.
</p>
<p>The project's official URL is <a
1.23 +6 -1 logging-log4j/src/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/logging-log4j/src/xdocs/stylesheets/project.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- project.xml 3 Jan 2005 15:26:57 -0000 1.22
+++ project.xml 29 Apr 2005 17:39:41 -0000 1.23
@@ -11,8 +11,9 @@
<item name="Introduction" href="/index.html"/>
<item name="Download" href="/download.html"/>
<item name="Documentation" href="/documentation.html"/>
+ <item name="Contact us" href="/contactUs.html"/>
+ <item name="Contributors" href="/contributors.html"/>
<item name="Chainsaw" href="/chainsaw.html"/>
- <item name="UGLI" href="/ugli.html"/>
<item name="History" href="/history.html"/>
</menu>
@@ -23,6 +24,10 @@
<item name="Bug Reporting" href="http://logging.apache.org/site/bugreport.html"/>
</menu>
+ <menu name="Related Projects">
+ <item name="SLF4J" href="http://www.slf4j.org"/>
+ </menu>
+
<menu name="Translations">
<item name="Korean" href="http://jakarta.apache-korea.org/log4j/index.html"/>
<item name="Japanese" href="http://www.ingrid.org/jajakarta/log4j/"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org