[logback-dev] svn commit: r2117 - in logback/trunk/logback-site/src/site/pages: . css manual
noreply.ceki at qos.ch
noreply.ceki at qos.ch
Tue Dec 30 15:55:44 CET 2008
Author: ceki
Date: Tue Dec 30 15:55:44 2008
New Revision: 2117
Modified:
logback/trunk/logback-site/src/site/pages/css/common.css
logback/trunk/logback-site/src/site/pages/faq.html
logback/trunk/logback-site/src/site/pages/manual/architecture.html
logback/trunk/logback-site/src/site/pages/manual/joran.html
logback/trunk/logback-site/src/site/pages/news.html
Log:
- added an FAQ entry relating to the location of config file on the class path.
- the section on logback initialization references the FAQ entry (location of config
files on the class path). This fixes LBSITE-20.
- minor enhancements in architecture.html relating to the basic selection rule
- updates to news.html
Modified: logback/trunk/logback-site/src/site/pages/css/common.css
==============================================================================
--- logback/trunk/logback-site/src/site/pages/css/common.css (original)
+++ logback/trunk/logback-site/src/site/pages/css/common.css Tue Dec 30 15:55:44 2008
@@ -168,6 +168,7 @@
font-size: 130%;
}
+
.green {
color: green;
}
@@ -176,10 +177,15 @@
background-color: #FFFFFF;
}
+.lgray_bg {
+ background-color: #EEE;
+}
+
.blue {
color: blue;
}
+
.red {
color: red;
}
Modified: logback/trunk/logback-site/src/site/pages/faq.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/faq.html (original)
+++ logback/trunk/logback-site/src/site/pages/faq.html Tue Dec 30 15:55:44 2008
@@ -47,6 +47,12 @@
</li>
<li>
+ <a href="#configFileLocation">Where should the configuration files,
+ <em>logback-test.xml</em> or <em>logback.xml</em>, be located
+ on the classpath?</a>
+ </li>
+
+ <li>
<a href="#sharedConfiguration">Is it possible for multiple JEE
applications to share the same configuration file but without
stepping on each other's toes?
@@ -86,7 +92,7 @@
in order to emphasize the fact that it is a related but
<em>different</em> project than log4j.
</p>
-
+
<p>Given that Java v7 will be distributed under GPL, we expect
GPL and LGPL to become even more prevalent in the Java world.
</p>
@@ -118,6 +124,30 @@
</dd>
+ <!-- ========================================================= -->
+
+ <dt>
+ <a name="configFileLocation" href="#configFileLocation">Where
+ should the configuration files, <em>logback-test.xml</em> or
+ <em>logback.xml</em>, be located on the classpath?</a>
+ </dt>
+
+ <dd>
+ <p>Configuration files such as <em>logback-test.xml</em> or
+ <em>logback.xml</em> can be located <b>directly</b> under
+ any folder declared in the class path. For example, if the
+ class path reads "c:/java/jdk15/lib/rt.jar;c:/mylibs/" then
+ the <em>logback.xml</em> file should be located directly
+ under "c:/mylibs/", that is as
+ "c:/mylibs/logback.xml". Placing it under a sub-folder of
+ c:/mylibs/, say, c:/mylibs/other/, will not work.</p>
+
+ <p>For web-applications, configuration files can be placed
+ <b>directly</b> under <em>WEB-INF/classes/</em>.</p>
+
+ <hr/>
+
+ </dd>
<!-- ========================================================= -->
Modified: logback/trunk/logback-site/src/site/pages/manual/architecture.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/manual/architecture.html (original)
+++ logback/trunk/logback-site/src/site/pages/manual/architecture.html Tue Dec 30 15:55:44 2008
@@ -344,58 +344,81 @@
<div class="definition">
<div class="deftitle">Basic Selection Rule</div>
- <p>A log request of level <em>p</em> issued with a logger having
- an effective level <em>q</em>, is enabled if <em>p >= q</em>.
+ <p>A log request of level <em>p</em> issued to a logger having
+ an effective level <em>q</em>, is enabled if
+ <em>p >= q</em>.
</p>
</div>
<p>This rule is at the heart of logback. It assumes that levels
- are ordered as follows: <code>DEBUG < INFO < WARN <
- ERROR</code>.
+ are ordered as follows:
+ <code>TRACE < DEBUG < INFO <
+ WARN < ERROR</code>.
</p>
<p>In a more graphic way, here is how the selection rule works. In
the following table, the vertical header shows the the level of
the logging request, designated by <em>p</em>, while the
horizontal header shows effective level of the logger, designated
- by <em>q</em>.
+ by <em>q</em>. The intersection of the rows (level request) and
+ columns (effective level) is the boolean resulting from the basic
+ selection rule.
</p>
- <table>
- <tr>
- <th><span style="align:center"><em>p</em>/<em>q</em></span></th>
- <th>DEBUG</th>
- <th>INFO</th>
- <th>WARN</th>
- <th>ERROR</th>
- <th>OFF</th>
+ <table width="80%">
+ <tr>
+ <td class="lgray_bg" rowspan="2">level of <br/>request <em>p</em></td>
+ <td style="border-top: 1px solid #DDDDDD;"
+ align="center" colspan="6">effective level <em>q</em></td>
+ </tr>
+ <tr align="left">
+ <th style="border-bottom: 1px solid #DDDDDD;">TRACE</th>
+ <th style="border-bottom: 1px solid #DDDDDD;">DEBUG</th>
+ <th style="border-bottom: 1px solid #DDDDDD;">INFO</th>
+ <th style="border-bottom: 1px solid #DDDDDD;">WARN</th>
+ <th style="border-bottom: 1px solid #DDDDDD;">ERROR</th>
+ <th style="border-bottom: 1px solid #DDDDDD;">OFF</th>
</tr>
- <tr>
- <th>DEBUG</th>
+ <tr align="left" >
+ <th class="lgray_bg">TRACE</th>
<td><span class="greenBold">YES</span></td>
<td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
+ <td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
</tr>
- <tr>
- <th>INFO</th>
+
+ <tr align="left">
+ <th class="lgray_bg">DEBUG</th>
<td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
<td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
+ <td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
</tr>
- <tr>
- <th>WARN</th>
+ <tr align="left" >
+ <th class="lgray_bg">INFO</th>
<td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
<td><span class="redBold">NO</span></td>
+ <td><span class="redBold">NO</span></td>
<td><span class="redBold">NO</span></td>
</tr>
- <tr>
- <th>ERROR</th>
+ <tr align="left" >
+ <th class="lgray_bg">WARN</th>
+ <td><span class="greenBold">YES</span></td>
+ <td><span class="greenBold">YES</span></td>
+ <td><span class="greenBold">YES</span></td>
+ <td><span class="greenBold">YES</span></td>
+ <td><span class="redBold">NO</span></td>
+ <td><span class="redBold">NO</span></td>
+ </tr>
+ <tr align="left" >
+ <th class="lgray_bg">ERROR</th>
+ <td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
<td><span class="greenBold">YES</span></td>
Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/manual/joran.html (original)
+++ logback/trunk/logback-site/src/site/pages/manual/joran.html Tue Dec 30 15:55:44 2008
@@ -79,12 +79,16 @@
<ol>
<li>
- <p>Logback tries to find a file called <em>logback-test.xml</em>
- in the classpath.</p>
+ <p>Logback tries to find a file called
+ <em>logback-test.xml</em> <a
+ href="../faq.html#configFileLocation">in the
+ classpath</a>.</p>
</li>
<li><p>If no such file is found, it checks for the file
- <em>logback.xml</em>.</p>
+ <em>logback.xml</em> <a
+ href="../faq.html#configFileLocation">in the
+ classpath</a>..</p>
</li>
<li><p>In case neither file is found, logback configures itself
Modified: logback/trunk/logback-site/src/site/pages/news.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/news.html (original)
+++ logback/trunk/logback-site/src/site/pages/news.html Tue Dec 30 15:55:44 2008
@@ -28,6 +28,24 @@
<hr width="80%" align="center" />
+ <h3>TARGET DATE: 26th of January 2009 - Release of version 0.9.15</h3>
+
+ <p>When the reset() method in <code>LoggerContext</code> is
+ called, registered turbo filters are first stopped before being
+ unregistered. This fixes <a
+ href="http://jira.qos.ch/browse/LBCLASSIC-89">LBCLASSIC-89</a>
+ reported by Alexis Morillo.
+ </p>
+
+ <p>Added the <code>clear()</code> mthod to the
+ <code>StatusManager</code> interface. After reconfiguration, it
+ may be desirable to clear the status list maintained by a
+ <code>StatusManager</code>. This change was requested by Alexis
+ Morillo in <a
+ href="http://jira.qos.ch/browse/LBCORE-77">LBCORE-77</a>.
+ </p>
+
+
<h3>29th of December 2008 - Release of version 0.9.14</h3>
More information about the logback-dev
mailing list