[logback-dev] [GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, encoder, updated. v0.9.18-38-g2d9abfa
added by portage for gitosis-gentoo
git-noreply at pixie.qos.ch
Mon Feb 22 12:57:27 CET 2010
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Logback: the generic, reliable, fast and flexible logging framework.".
The branch, encoder has been updated
via 2d9abfae52400cf99ce88470cdf85fb45046b60e (commit)
from 8270ffa0f18e65c70d176d30b71cf748845e0441 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=2d9abfae52400cf99ce88470cdf85fb45046b60e
http://github.com/ceki/logback/commit/2d9abfae52400cf99ce88470cdf85fb45046b60e
commit 2d9abfae52400cf99ce88470cdf85fb45046b60e
Author: Ceki Gulcu <ceki at qos.ch>
Date: Mon Feb 22 12:54:48 2010 +0100
- marketing...
diff --git a/logback-site/src/site/pages/documentation.html b/logback-site/src/site/pages/documentation.html
index 7dbcef3..29f4e95 100644
--- a/logback-site/src/site/pages/documentation.html
+++ b/logback-site/src/site/pages/documentation.html
@@ -28,6 +28,9 @@
<ul>
<li><a href="manual/index.html"><b>The logback manual</b></a></li>
+ <li><a href="reasonsToSwitch.html">Reasons to switch to logback
+ from log4j</a></li>
+
<li>
<a href="access.html">An introduction to logback-access for Jetty
and Tomcat</a>
diff --git a/logback-site/src/site/pages/index.html b/logback-site/src/site/pages/index.html
index b5293b9..7fa648c 100644
--- a/logback-site/src/site/pages/index.html
+++ b/logback-site/src/site/pages/index.html
@@ -22,7 +22,8 @@
<h2>Logback Project</h2>
<p>Logback is intended as a successor to the popular log4j
- project, picking up where log4j left off.
+ project, <a href="reasonsToSwitch.html">picking up where log4j
+ left off</a>.
</p>
<p>Logback's basic architecture is sufficiently generic so as to
diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html
index 9a273c6..fa89892 100644
--- a/logback-site/src/site/pages/manual/appenders.html
+++ b/logback-site/src/site/pages/manual/appenders.html
@@ -3384,8 +3384,7 @@ logger.error(<b>notifyAdminMarker</b>,
attribute. For example, <code>SiftingAppender</code> can separate
logging events according to user sessions, so that the logs
generated by every user go into distinct log files, one log file
- per user. For example, <code>SiftingAppender</code> can separate
- logging events into distinct log files, one file per user.
+ per user.
</p>
diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html
new file mode 100644
index 0000000..26b0381
--- /dev/null
+++ b/logback-site/src/site/pages/reasonsToSwitch.html
@@ -0,0 +1,180 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
+ <title>Reasons to prefer logback</title>
+ <link rel="stylesheet" type="text/css" href="css/common.css" />
+ <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" />
+ <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" />
+
+ </head>
+ <body>
+ <script type="text/javascript">prefix='';</script>
+ <script src="templates/header.js" type="text/javascript"></script>
+ <div id="left">
+ <noscript>Please turn on Javascript to view this menu</noscript>
+ <script src="templates/left.js" type="text/javascript"></script>
+ </div>
+ <div id="content">
+
+ <h2>Reasons to prefer logback over log4j</h2>
+
+ <p>Here is a non-exhaustive list of reasons for switching to
+ logback from log4j. Keep in mind that logback is conceptually very
+ similar to log4j. If you are already familiar with log4j, you will
+ quickly feel at home using logback.</p>
+
+ <h3><a name="fasterImpl" href="#fasterImpl">Faster implementation</a></h3>
+
+ <p>Based on our previous work done on log4j, logback internals
+ have been re-written to perform about ten times faster on certain
+ critical execution paths. Not only do logback components are
+ faster, they have a smaller memory footprint as well.</p>
+
+ <h3><a name="tdd" href="#tdd">Extensive battery of tests</a></h3>
+
+ <p>Logback comes with a very extensive battery of tests developed
+ over the course of several years and untold hours of work. While
+ log4j is also tested, logback takes testing to a completely
+ different level. In our opinion, this is the single most important
+ reason to prefer logback over log4j. You want your logging
+ framework to be rock solid and dependable even under adverse
+ conditions.
+ </p>
+
+ <h3><a name="slf4j" href="#slf4j">logback-classic speaks SLF4J
+ natively</a></h3>
+
+ <p>Since the <code>Logger</code> class in logback-classic
+ implements the SLF4J API natively, you incur zero overhead when
+ invoking an SLF4J logger with logback-classic as the underlying
+ implementation. Moreover, since logback-classic strongly
+ encourages the use of SLF4J as its client API, if you need to
+ switch to log4j or to j.u.l., you can do so by replacing one jar
+ file with another. You will not need to touch your code logging
+ via the SLF4J API. This can drastically reduce the work involved
+ in switching logging frameworks.
+ </p>
+
+ <h3><a name="docs" href="#docs">Extensive documentation</a></h3>
+
+ <p>Logback ships with over two hundred pages of documentation.</p>
+
+ <h3><a name="autoScan" href="#autoScan">Automatic reloading of
+ configuration files</a></h3>
+
+ <p>Logback-classic can <a
+ href="manual/configuration.html#autoScan">automatically reload its
+ configuration file upon modification</a>. The scanning process is
+ both fast and safe as it does <em>not</em> involve the creation of
+ a separate scanning-thread. This technical subtlety ensures that
+ logback plays well within application servers and more generally
+ within the JEE environment.</p>
+
+
+ <h3><a name="lilith" href="#lilith">Lilith</a></h3>
+
+ <p><a href="http://lilith.huxhorn.de/">Lilith</a> is a logging and
+ access event viewer for logback. It is comparable to log4j's
+ chainsaw, except that Lilith is designed to handle large amounts of
+ logging data without flinching.</p>
+
+ <h3><a name="grace" href="#grace">Prudent mode and graceful recovery</a></h3>
+
+ <p>In <a href="manual/appenders.html#prudent">prudent mode</a>,
+ multiple <code>FileAppender</code> instances running on multiple
+ JVMs can safely write to the same log file. With certain
+ limitations, prudent mode extends to
+ <code>RollingFileAppender</code>.
+ </p>
+
+ <p>Logback's <code>FileAppender</code> all its sub-classes
+ including <code>RollingFileAppender</code> can gracefully recover
+ from I/O failures. Thus, if a file server fails temporarily, you
+ no longer need to restart your application just to repair logging.
+ </p>
+
+
+ <h3><a name="filters" href="#filters">Filters</a></h3>
+
+ <p>Logback comes with a wide array of <a
+ href="manual/filters.html">filtering capabilities</a> going much
+ further than what log4j has to offer. For example, let's assume
+ that you have a business-critical application deployed on a
+ production server. Given the large volume of transactions,
+ logging level is set to WARN so that only warnings and errors are
+ logged. Now imagine that you are confronted with a bug that can be
+ reproduced on the production system but remains elusive on the
+ test platform due to unspecified differences between the two
+ environments (production/testing).
+ </p>
+
+ <p>With log4j, your only choice is to lower the logging level to
+ DEBUG on the production system in an attempt to identify the
+ problem. Unfortunately, this will generate large volume of logging
+ data, making analysis difficult. More importantly, extensive
+ logging can impact the performance of you application on the
+ production system.</p>
+
+ <p>With logback, you have the option of keeping logging at the
+ WARN level for all users except for the one user, say Alice, who
+ is responsible for identifying the problem. When Alice is logged
+ on, she will be logging at level DEBUG while for other users
+ logging will remain at WARN. This feat can be accomplished by
+ adding 4 lines of XML to your configuration file. Search for
+ <code>MDCFilter</code> in the <a
+ href="manual/filters.html#TurboFilter">relevant section</a> of
+ the manual.
+ </p>
+
+
+ <h3><a name="sift" href="#sift">SiftingAppender</a></h3>
+
+ <p><a
+ href="manual/appenders.html#SiftingAppender">SiftingAppender</a>
+ is an amazingly versatile appender. It can be used to separate (or
+ sift) logging according to any given runtime attribute. For
+ example, <code>SiftingAppender</code> can separate logging events
+ according to user sessions, so that the logs generated by each
+ user go into distinct log files, one log file per user.
+ </p>
+
+ <h3><a name="compression" href="#compression">Automatic
+ compression of archives log files</a></h3>
+
+ <p><a href="manual/appenders.html#RollingFileAppender">RollingFileAppender</a> can automatically
+ compression archived log files during rollover. Compression always
+ occurs asynchronously so that even for large log files your
+ application is not blocked for the duration of the compression.
+ </p>
+
+
+ <h3><a name="maxHistory" href="#maxHistory">Automatic erasing of
+ old log files</a></h3>
+
+ <p>By setting the <span class="option">MaxHistory</span> property
+ of <a
+ href="manual/appenders.html#TimeBasedRollingPolicy">TimeBasedRollingPolicy</a>
+ or <a
+ href="manual/appenders.html#SizeAndTimeBasedFNATP">SizeAndTimeBasedFNATP</a>,
+ you can control the maximum number of archived files. If your
+ rolling policy calls for monthly rollover and you wish to keep 1
+ year's worth of logs, simply set the <span
+ class="option">MaxHistory</span> property to 12. Archived log
+ files older than 12 months will be automatically removed.
+ </p>
+
+
+ <h3><a href="">In summary</a></h3>
+
+ <p>We have listed a small number of reasons for preferring logback
+ over log4j. Given that logback builds upon the log4j experience,
+ to put it simply, logback is just a better log4j.</p>
+
+ <script src="templates/footer.js" type="text/javascript"></script>
+ </div>
+
+ </body>
+</html>
\ No newline at end of file
diff --git a/logback-site/src/site/pages/templates/footer.js b/logback-site/src/site/pages/templates/footer.js
index f97c725..c548cab 100644
--- a/logback-site/src/site/pages/templates/footer.js
+++ b/logback-site/src/site/pages/templates/footer.js
@@ -1,6 +1,10 @@
document.write('<table class="footer">')
+
+
+document.write('</tr>')
+
document.write('<tr>')
document.write(' <td>')
@@ -10,8 +14,13 @@ document.write(' ')
//document.write(' alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>')
document.write(' </td>')
-document.write('<td valign="top">Copyright © 1999-2010 <a href="http://www.qos.ch/">QOS.ch</a></td>')
-
+document.write('<td valign="top">Copyright © 2010 <a href="http://www.qos.ch/">QOS.ch</a></td>')
document.write('</tr>')
+
+document.write('<tr>')
+document.write('<td align="left" colspan="2">')
+document.write('We are actively looking for volunteers to proofread the documentation. Please send your corrections or suggestions for improvement to "corrections at qos.ch".');
+document.write('</td>')
+
document.write('</table>')
-----------------------------------------------------------------------
Summary of changes:
logback-site/src/site/pages/documentation.html | 3 +
logback-site/src/site/pages/index.html | 3 +-
logback-site/src/site/pages/manual/appenders.html | 3 +-
logback-site/src/site/pages/reasonsToSwitch.html | 180 +++++++++++++++++++++
logback-site/src/site/pages/templates/footer.js | 13 ++-
5 files changed, 197 insertions(+), 5 deletions(-)
create mode 100644 logback-site/src/site/pages/reasonsToSwitch.html
hooks/post-receive
--
Logback: the generic, reliable, fast and flexible logging framework.
More information about the logback-dev
mailing list