logging-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From grobme...@apache.org
Subject svn commit: r822469 [4/5] - in /websites/production/loggingtest/content/log4cxx: ./ log4cxx-0.11.0-SNAPSHOT/ log4cxx-0.11.0-SNAPSHOT/building/ log4cxx-0.11.0-SNAPSHOT/css/ log4cxx-0.11.0-SNAPSHOT/images/ log4cxx-0.11.0-SNAPSHOT/images/logos/ log4cxx-0....
Date Wed, 20 Jun 2012 09:25:04 GMT
Added: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/index.html
==============================================================================
--- websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/index.html (added)
+++ websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/index.html Wed Jun 20 09:25:02 2012
@@ -0,0 +1,1086 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+-->
+<!-- Generated by Apache Maven Doxia at Jun 20, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+    <title>
+    Short introduction to Apache log4cxx</title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <meta name="Date-Revision-yyyymmdd" content="20120620" />
+    <meta http-equiv="Content-Language" content="en" />
+      </head>
+  <body class="composite">
+    <div id="banner">
+                  <a href="http://logging.apache.org/" id="bannerLeft">
+                                                <img src="images/ls-logo.jpg" alt="Logging Services" />
+                </a>
+                    <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="breadcrumbs">
+            
+        
+                <div class="xleft">
+        <span id="publishDate">Last Published: 2012-06-20</span>
+                  &nbsp;| <span id="projectVersion">Version: 0.11.0-SNAPSHOT</span>
+                          |                           <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+                &gt;
+                              <a href="http://logging.apache.org/" class="externalLink" title="Logging Services">Logging Services</a>
+                &gt;
+                              <a href="./" title="log4cxx">log4cxx</a>
+                          </div>
+            <div class="xright">        
+        
+      </div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="leftColumn">
+      <div id="navcolumn">
+             
+        
+                                <h5>Get Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="download.html" title="Download">Download</a>
+            </li>
+                  <li class="none">
+                          <a href="changes-report.html" title="Changes">Changes</a>
+            </li>
+                  <li class="none">
+                          <a href="license.html" title="License">License</a>
+            </li>
+          </ul>
+                       <h5>About Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+            <strong>What is log4cxx?</strong>
+          </li>
+                  <li class="none">
+                          <a href="apidocs/index.html" title="API Documentation">API Documentation</a>
+            </li>
+                  <li class="none">
+                          <a href="faq.html" title="FAQ">FAQ</a>
+            </li>
+          </ul>
+                       <h5>Community</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+            </li>
+                  <li class="none">
+                          <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+            </li>
+                  <li class="none">
+                          <a href="http://wiki.apache.org/logging-log4cxx" class="externalLink" title="Wiki">Wiki</a>
+            </li>
+          </ul>
+                       <h5>Development</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="source-repository.html" title="Repository">Repository</a>
+            </li>
+                                                                                                                                      <li class="expanded">
+                          <a href="#" title="Building">Building</a>
+                    <ul>
+                      <li class="none">
+                          <a href="building/autotools.html" title="autotools">autotools</a>
+            </li>
+                      <li class="none">
+                          <a href="building/ant.html" title="Apache Ant">Apache Ant</a>
+            </li>
+                      <li class="none">
+                          <a href="building/maven.html" title="Apache Maven 2">Apache Maven 2</a>
+            </li>
+                      <li class="none">
+                          <a href="building/vstudio.html" title="Microsoft Visual Studio">Microsoft Visual Studio</a>
+            </li>
+                      <li class="none">
+                          <a href="building/xcode.html" title="Apple Xcode">Apple Xcode</a>
+            </li>
+              </ul>
+        </li>
+          </ul>
+                       <h5>Apache</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="http://www.apache.org" class="externalLink" title="Home">Home</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsorship">Sponsorship</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apachecon.com" class="externalLink" title="Conferences">Conferences</a>
+            </li>
+          </ul>
+                             <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+        <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+      </a>
+                   
+        
+            </div>
+    </div>
+    <div id="bodyColumn">
+      <div id="contentBox">
+        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License. -->
+
+  
+<div class="section"><h2>Short introduction to Apache log4cxx<a name="Short_introduction_to_Apache_log4cxx"></a></h2>
+
+<div class="section"><h2>Introduction<a name="Introduction"></a></h2>
+
+Apache log4cxx is a logging framework for C++ patterned after 
+<a class="externalLink" href="http://logging.apache.org/log4j">Apache log4j</a>.
+Apache log4cxx uses <a class="externalLink" href="http://apr.apache.org">Apache Portable Runtime</a>
+for most platform-specific code and should be usable on any
+platform supported by APR.  Apache log4cxx is licensed under the 
+<a class="externalLink" href="http://www.apache.org/licenses/">Apache License</a>,
+an open source license certified by the 
+<a class="externalLink" href="http://www.opensource.org/">Open Source Initiative</a>.
+
+<p>Almost every large application includes its own logging or tracing
+API.   Inserting log statements into code is a low-tech method for
+debugging it. It may also be the only way because debuggers are not
+always available or applicable. This is usually the case for
+multithreaded applications and distributed applications at large.</p>
+
+<p>Experience indicates that logging is an important component of the
+development cycle. It offeres several advantages. It provides precise
+<i>context</i> about a run of the application. Once inserted into
+the code, the generation of logging output requires no human
+intervention.  Moreover, log output can be saved in persistent medium
+to be studied at a later time. In addition to its use in the
+development cycle, a sufficiently rich logging package can also be
+viewed as an auditing tool.</p>
+
+<p>Logging does have its drawbacks. It can slow down an
+application. If too verbose, it can cause scrolling blindness. To
+alleviate these concerns, log4cxx is designed to be reliable, fast and
+extensible. Since logging is rarely the main focus of an application,
+the log4cxx API strives to be simple to understand and to use.</p>
+
+<div class="section"><h2>Loggers, Appenders and Layouts<a name="Loggers_Appenders_and_Layouts"></a></h2>
+
+<p>Log4cxx has three main components: <i>loggers</i>,
+<i>appenders</i> and <i>layouts</i>. These three types of
+components work together to enable developers to log messages according
+to message type and level, and to control at runtime how these
+messages are formatted and where they are reported.</p>
+
+<div class="section"><h3>Logger hierarchy<a name="Logger_hierarchy"></a></h3>
+
+<p>The first and foremost advantage of any logging API over plain
+<tt>std::cout</tt> resides in its ability to disable
+certain log statements while allowing others to print unhindered. This
+capability assumes that the logging space, that is, the space of all
+possible logging statements, is categorized according to some
+developer-chosen criteria.</p>
+
+<p>Loggers are named entities. Logger names are case-sensitive and
+they follow the hierarchical naming rule:</p>
+
+<p>
+</p><table border="0" class="bodyTable" bgcolor="#EEEE99">
+ <tr class="a">
+  <td>
+   <dl>
+     <dt><b>Named Hierarchy</b></dt>
+
+     <dd>A logger is said to be an <i>ancestor</i> of another
+     logger if its name followed by a dot is a prefix of the
+     <i>descendant</i> logger name. A logger is said to be a
+     <i>parent</i> of a <i>child</i> logger if there are no
+     ancestors between itself and the descendant logger.</dd>
+
+
+   </dl>
+</td></tr></table>
+
+
+<p>For example, the logger named <tt>&quot;com.foo&quot;</tt> is a parent
+of the logger named <tt>&quot;com.foo.Bar&quot;</tt>.  Similarly,
+<tt>&quot;java&quot;</tt> is a parent of <tt>&quot;java.util&quot;</tt> and an
+ancestor of <tt>&quot;java.util.Vector&quot;</tt>.  This naming scheme
+should be familiar to most developers.</p>
+
+<p>The root logger resides at the top of the logger hierarchy. It
+is exceptional in two ways:
+
+</p><ol style="list-style-type: decimal">
+<li> it always exists,</li>
+<li> it cannot be retrieved by name.</li>
+</ol>
+<p>Invoking the class static <a href="apidocs/classlog4cxx_1_1Logger.html#e3">log4cxx::Logger::getRootLogger</a>
+method retrieves it. All other loggers are instantiated and
+retrieved with the class static <a href="apidocs/classlog4cxx_1_1Logger.html#e0">log4cxx::Logger::getLogger</a>
+method. This method takes the name of the desired logger as a
+parameter. Some of the basic methods in the Logger class are listed
+below.</p>
+
+<p></p><table border="0" class="bodyTable">
+<tr class="a" bgcolor="CCCCCC">
+<td>
+<div><pre>
+  namespace log4cxx {
+
+    class <b>Logger</b> {
+       public:
+       // Creation &amp; retrieval methods:
+       static LoggerPtr getRootLogger();
+       static LoggerPtr getLogger(const std::string&amp; name);
+       static LoggerPtr getLogger(const std::wstring&amp; name);
+
+     }
+   }
+//
+//   Use these macros instead of calling Logger methods directly.
+//   Macros will handle char or wchar_t pointers or strings
+//   or most right-hand side expressions of an 
+//   std::basic_string::operator&lt;&lt;.
+//   
+#define LOG4CXX_TRACE(logger, expression) ...   
+#define LOG4CXX_DEBUG(logger, expression) ...   
+#define LOG4CXX_INFO(logger, expression) ...   
+#define LOG4CXX_WARN(logger, expression) ...   
+#define LOG4CXX_ERROR(logger, expression) ...   
+#define LOG4CXX_FATAL(logger, expression) ...   
+</pre></div>
+</td>
+</tr>
+</table>
+
+<p>Loggers <i>may</i> be assigned levels. The pre-defined
+levels: TRACE, DEBUG, INFO, WARN, ERROR and FATAL are defined in the <tt><a href="apidocs/classlog4cxx_1_1Level.html">log4cxx::Level</a></tt>
+class which provides accessor functions.</p>
+
+<p>If a given logger is not assigned a level, then it inherits
+one from its closest ancestor with an assigned level. More
+formally:</p>
+
+
+<p>
+</p><table border="0" class="bodyTable" bgcolor="#EEEE99">
+  <tr class="a">
+  <td>
+   <dl>
+     <dt><b>Level Inheritance</b></dt>
+
+     <dd><p>The <i>inherited level</i> for a given logger
+<i>C</i>, is equal to the first non-null level in the logger
+hierarchy, starting at <i>C</i> and proceeding upwards in the
+hierarchy towards the <tt>root</tt> logger.</p></dd>
+
+   </dl>
+   </td>
+   </tr>
+</table>
+
+<p>To ensure that all loggers can eventually inherit a level,
+the root logger always has an assigned level.</p>
+
+<p>Below are four tables with various assigned level values and the
+resulting inherited levels according to the above rule.</p>
+
+<p>
+</p><caption align="bottom">Example 1</caption><table class="bodyTable" border="1">
+  <tr class="a"><th>Logger<br />name</th><th>Assigned<br />level</th>
+    <th>Inherited<br />level</th></tr>
+    <tr class="b" align="left"><td>root</td>    <td>Proot</td> <td>Proot</td></tr>
+    <tr class="a" align="left"><td>X </td>      <td>none</td>  <td>Proot</td></tr>
+    <tr class="b" align="left"><td>X.Y </td>    <td>none</td>  <td>Proot</td></tr>
+    <tr class="a" align="left"><td>X.Y.Z</td>   <td>none</td>  <td>Proot</td></tr>
+    
+</table>
+
+<p>In example 1 above, only the root logger is assigned a
+level. This level value, <tt>Proot</tt>, is inherited by the
+other loggers <tt>X</tt>, <tt>X.Y</tt> and
+<tt>X.Y.Z</tt>.</p>
+
+
+<p>
+</p><caption align="bottom">Example 2</caption><table class="bodyTable" border="1">
+    <tr class="a"><th>Logger<br />name</th><th>Assigned<br />level</th>
+    <th>Inherited<br />level</th></tr>
+    <tr class="b" align="left"><td>root</td>    <td>Proot</td> <td>Proot</td></tr>
+    <tr class="a" align="left"><td>X </td>      <td>Px</td>    <td>Px</td></tr>
+    <tr class="b" align="left"><td>X.Y </td>    <td>Pxy</td>   <td>Pxy</td></tr>
+    <tr class="a" align="left"><td>X.Y.Z</td>   <td>Pxyz</td>  <td>Pxyz</td></tr>
+    
+  </table>
+
+<p>In example 2, all loggers have an assigned level value. There
+is no need for level inheritence.</p>
+
+<p></p><caption align="bottom">Example 3</caption><table class="bodyTable" border="1">
+    <tr class="a"><th>Logger<br />name</th><th>Assigned<br />level</th>
+    <th>Inherited<br />level</th></tr>
+    <tr class="b" align="left"><td>root</td>    <td>Proot</td> <td>Proot</td></tr>
+    <tr class="a" align="left"><td>X </td>      <td>Px</td>    <td>Px</td></tr>
+    <tr class="b" align="left"><td>X.Y </td>    <td>none</td>  <td>Px</td></tr>
+    <tr class="a" align="left"><td>X.Y.Z</td>   <td>Pxyz</td>  <td>Pxyz</td></tr>
+    
+</table>
+
+<p>In example 3, the loggers <tt>root</tt>, <tt>X</tt> and
+<tt>X.Y.Z</tt> are assigned the levels <tt>Proot</tt>,
+<tt>Px</tt> and <tt>Pxyz</tt> respectively. The logger
+<tt>X.Y</tt> inherits its level value from its parent
+<tt>X</tt>.</p>
+
+<table class="bodyTable" border="1"><caption align="bottom">Example 4</caption>
+    <tr class="a"><th>Logger<br />name</th><th>Assigned<br />level</th>
+    <th>Inherited<br />level</th></tr>
+    <tr class="b" align="left"><td>root</td>    <td>Proot</td> <td>Proot</td></tr>
+    <tr class="a" align="left"><td>X </td>      <td>Px</td>    <td>Px</td></tr>
+    <tr class="b" align="left"><td>X.Y </td>    <td>none</td>  <td>Px</td></tr>
+    <tr class="a" align="left"><td>X.Y.Z</td>   <td>none</td>  <td>Px</td></tr>
+    
+</table>
+
+<p>In example 4, the loggers <tt>root</tt> and <tt>X</tt>
+and are assigned the levels <tt>Proot</tt> and <tt>Px</tt>
+respectively. The loggers <tt>X.Y</tt> and <tt>X.Y.Z</tt>
+inherits their level value from their nearest parent <tt>X</tt>
+having an assigned level.</p>
+
+
+<p>Logging requests are made by invoking a method of
+a logger instance, preferrably through the use of LOG4CXX_INFO or similar
+macros which support short-circuiting if the threshold is not satisfied
+and use of the insertion operator (&lt;&lt;) in the message parameter.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCCCCC"><tr class="a"><td><div><pre>
+   log4cxx::LoggerPtr logger(log4cxx::Logger::getLogger(<b>&quot;com.foo&quot;</b>));
+   const char* region = &quot;World&quot;;
+   LOG4CXX_INFO(logger, &quot;Simple message text.&quot;)
+   LOG4CXX_INFO(logger, &quot;Hello, &quot; &lt;&lt; region)
+   LOG4CXX_DEBUG(logger, L&quot;Iteration &quot; &lt;&lt; i)
+   LOG4CXX_DEBUG(logger, &quot;e^10 = &quot; &lt;&lt; std::scientific &lt;&lt; exp(10.0))
+   //
+   //  Use a wchar_t first operand to force use of wchar_t based stream.    
+   //
+   LOG4CXX_WARN(logger, L&quot;&quot; &lt;&lt; i &lt;&lt; L&quot; is the number of the iteration.&quot;)
+</pre></div></td></tr></table>
+
+<p>A logging request is said to be <i>enabled</i> if its level is
+higher than or equal to the level of its logger. Otherwise, the
+request is said to be <i>disabled</i>. A logger without an
+assigned level will inherit one from the hierarchy. This rule is
+summarized below.</p>
+
+
+<p>
+<a name="selectionRule"></a></p><table border="0" class="bodyTable" bgcolor="#EEEE99">
+  <tr class="a">
+  <td>
+      <dl>
+	<dt><b>Basic Selection Rule</b></dt>
+
+	<dd><p>A log request of level <i>p</i> in a logger with
+	(either assigned or inherited, whichever is appropriate) level <i>q</i>, is enabled if <i> p &gt;=
+	q</i>.</p></dd>
+      </dl>
+</td></tr></table>
+
+<p>This rule is at the heart of log4cxx. It assumes that levels are
+ordered. For the standard levels, we have <tt>TRACE &lt; DEBUG &lt; INFO
+&lt; WARN &lt; ERROR &lt; FATAL</tt>.</p>
+
+<p>Here is an example of this rule.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCCCCC">
+<tr class="a"><td>
+<div><pre>
+
+   // get a logger instance named &quot;com.foo&quot;
+   log4cxx::LoggerPtr  logger(log4cxx::Logger::getLogger(<b>&quot;com.foo&quot;</b>));
+
+   // Now set its level. Normally you do not need to set the
+   // level of a logger programmatically. This is usually done
+   // in configuration files.
+   <b>logger</b>-&gt;setLevel(<font color="0000AA"><b>log4cxx::Level::getInfo()</b></font>);
+
+   log4cxx::LoggerPtr barlogger(log4cxx::Logger::getLogger(<b>&quot;com.foo.Bar&quot;</b>);
+
+   // This request is enabled, because <font color="00AA00"><b>WARN</b></font> &gt;= <font color="0000AA"><b>INFO</b></font>.
+   LOG4CXX_WARN(logger, &quot;Low fuel level.&quot;)
+
+   // This request is disabled, because <font color="00AA00"><b>DEBUG</b></font> &lt; <font color="0000AA"><b>INFO</b></font>.
+   LOG4CXX_DEBUG(logger, &quot;Starting search for nearest gas station.&quot;)
+
+   // The logger instance barlogger, named &quot;com.foo.Bar&quot;,
+   // will inherit its level from the logger named
+   // &quot;com.foo&quot; Thus, the following request is enabled
+   // because <font color="00AA00"><b>INFO</b></font> &gt;= <font color="0000AA"><b>INFO</b></font>.
+   LOG4CXX_INFO(barlogger. &quot;Located nearest gas station.&quot;)
+
+   // This request is disabled, because <font color="00AA00"><b>DEBUG</b></font> &lt; <font color="0000AA"><b>INFO</b></font>.
+   LOG4CXX_DEBUG(barlogger, &quot;Exiting gas station search&quot;)
+</pre></div>
+</td></tr>
+</table>
+
+<p>Calling the <tt>getLogger</tt> method with the same name will
+always return a reference to the exact same logger object.</p>
+
+<p>For example, in
+
+</p><table border="0" class="bodyTable" bgcolor="CCCCCC">
+<tr class="a"><td>
+<div><pre>
+   log4cxx::LoggerPtr x = log4cxx::Logger::getLogger(&quot;wombat&quot;);
+   log4cxx::LoggerPtr y = log4cxx::Logger::getLogger(&quot;wombat&quot;);</pre></div>
+</td></tr>
+</table>
+<tt>x</tt> and <tt>y</tt> refer to <i>exactly</i> the same
+logger object.
+
+<p>Thus, it is possible to configure a logger and then to retrieve
+the same instance somewhere else in the code without passing around
+references. In fundamental contradiction to biological parenthood,
+where parents always preceed their children, log4cxx loggers can be
+created and configured in any order. In particular, a &quot;parent&quot;
+logger will find and link to its descendants even if it is
+instantiated after them.</p>
+
+<p>Configuration of the log4cxx environment is typically done at
+application initialization. The preferred way is by reading a
+configuration file. This approach will be discussed shortly.</p>
+
+<p>Log4cxx makes it easy to name loggers by <i>software
+component</i>.  This can be accomplished by statically instantiating
+a logger in each class, with the logger name equal to the fully
+qualified name of the class. This is a useful and straightforward
+method of defining loggers. As the log output bears the name of the
+generating logger, this naming strategy makes it easy to identify
+the origin of a log message.  However, this is only one possible,
+albeit common, strategy for naming loggers. Log4cxx does not restrict
+the possible set of loggers. The developer is free to name the
+loggers as desired.</p>
+
+<p>Nevertheless, naming loggers after the class where they are
+located seems to be the best strategy known so far.</p>
+
+</div><div class="section"><h2>Appenders and Layouts<a name="Appenders_and_Layouts"></a></h2>
+
+<p>The ability to selectively enable or disable logging requests based
+on their logger is only part of the picture. Log4cxx allows logging
+requests to print to multiple destinations. In log4cxx speak, an output
+destination is called an <i>appender</i>. Currently, appenders exist
+for the <a href="apidocs/classlog4cxx_1_1ConsoleAppender.html">console</a>, <a href="apidocs/classlog4cxx_1_1FileAppender.html">files</a>, GUI
+components, <a href="apidocs/classlog4cxx_1_1net_1_1SocketAppender.html">remote socket</a>
+servers,  <a href="apidocs/classlog4cxx_1_1nt_1_1NTEventLogAppender.html"> NT
+Event Loggers</a>, and remote UNIX <a href="apidocs/classlog4cxx_1_1net_1_1SyslogAppender.html">Syslog</a>
+daemons. It is also possible to log <a href="apidocs/classlog4cxx_1_1AsyncAppender.html">asynchronously</a>.</p>
+
+<p>More than one appender can be attached to a logger.</p>
+
+<p>The <a href="apidocs/classlog4cxx_1_1Logger.html#a3">addAppender</a>
+method adds an appender to a given logger.
+
+<b>Each enabled logging
+request for a given logger will be forwarded to all the appenders in
+that logger as well as the appenders higher in the hierarchy.</b> In
+other words, appenders are inherited additively from the logger
+hierarchy. For example, if a console appender is added to the root
+logger, then all enabled logging requests will at least print on the
+console. If in addition a file appender is added to a logger, say
+<i>C</i>, then enabled logging requests for <i>C</i> and
+<i>C</i>'s children will print on a file <i>and</i> on the
+console. It is possible to override this default behavior so that
+appender accumulation is no longer additive by <a href="apidocs/classlog4cxx_1_1Logger.html#a46">setting
+the additivity flag</a> to <tt>false</tt>.</p>
+
+<p>The rules governing appender additivity are summarized below.</p>
+
+<p>
+<a name="additivity"></a></p><table border="0" class="bodyTable" bgcolor="#EEEE99">
+  <tr class="a">
+  <td>
+      <dl>
+	<dt><b>Appender Additivity</b></dt>
+
+	<dd><p>The output of a log statement of logger <i>C</i> will
+	go to all the appenders in <i>C</i> and its ancestors. This is
+	the meaning of the term &quot;appender additivity&quot;.</p>
+
+	<p>However, if an ancestor of logger <i>C</i>, say <i>P</i>,
+	has the additivity flag set to <tt>false</tt>, then
+	<i>C</i>'s output will be directed to all the appenders in
+	<i>C</i> and it's ancestors upto and including <i>P</i> but
+	not the appenders in any of the ancestors of <i>P</i>.</p>
+
+	<p>Loggers have their additivity flag set to
+	<tt>true</tt> by default.</p></dd>
+      </dl></td></tr>
+</table>
+
+
+<p>The table below shows an example:</p>
+
+<p></p><table class="bodyTable" align="center" border="3" cellpadding="10">
+  <tr class="a">
+  <th>Logger<br />Name </th><th>Added<br />Appenders</th> <th>Additivity<br />Flag</th> <th>Output Targets</th> <th>Comment</th>
+  </tr>
+<tr class="b"><td>root    </td><td>A1         </td><td>not applicable </td><td>A1</td>
+
+    <td>The root logger is anonymous but can be accessed with the
+        log4cxx::Logger::getRootLogger() method. There is no default appender
+        attached to root.</td></tr>
+
+<tr class="a"><td>x       </td><td>A-x1, A-x2 </td><td>true </td><td>A1, A-x1, A-x2</td>
+    <td>Appenders of &quot;x&quot; and root.</td></tr>
+
+<tr class="b"><td>x.y     </td><td>none       </td><td>true </td><td>A1, A-x1, A-x2</td>
+    <td>Appenders of &quot;x&quot; and root.</td></tr>
+
+<tr class="a"><td>x.y.z   </td><td>A-xyz1     </td><td>true </td><td>A1, A-x1, A-x2, A-xyz1</td>
+    <td>Appenders in &quot;x.y.z&quot;, &quot;x&quot; and root.</td></tr>
+
+<tr class="b"><td>security        </td><td>A-sec	   </td><td><font color="blue">false</font></td>
+                                           <td>A-sec</td>
+
+    <td>No appender accumulation since the additivity flag is set to
+        <tt>false</tt>.</td></tr>
+
+<tr class="a"><td>security.access </td><td>none </td><td> true </td><td> A-sec </td><td>Only
+    appenders of &quot;security&quot; because the additivity flag in &quot;security&quot; is
+    set to <tt>false</tt>.</td></tr>
+
+</table>
+
+
+<p>More often than not, users wish to customize not only the output
+destination but also the output format. This is accomplished by
+associating a <i>layout</i> with an appender. The layout is
+responsible for formatting the logging request according to the user's
+wishes, whereas an appender takes care of sending the formatted output
+to its destination.</p>
+
+The <a href="apidocs/classlog4cxx_1_1PatternLayout.html">PatternLayout</a>, part
+of the standard log4cxx distribution, lets the user specify the output
+format according to conversion patterns similar to the C language
+<tt>printf</tt> function.
+
+<p>For example, the PatternLayout with the conversion pattern &quot;%r [%t]
+%-5p %c - %m%n&quot; will output something akin to:<br />
+
+</p><div><pre>
+176 [main] INFO  org.foo.Bar - Located nearest gas station.
+</pre></div>
+
+<p>The first field is the number of milliseconds elapsed since the
+start of the program.  The second field is the thread making the log
+request.  The third field is the level of the log statement. The
+fourth field is the name of the logger associated with the log
+request. The text after the '-' is the message of the statement.</p>
+
+
+<div class="section"><h2>Configuration<a name="Configuration"></a></h2>
+
+<p>Inserting log requests into the application code requires a fair
+amount of planning and effort. Observation shows that approximately 4
+percent of code is dedicated to logging. Consequently, even moderately
+sized applications will have thousands of logging statements embedded
+within their code.  Given their number, it becomes imperative to
+manage these log statements without the need to modify them manually.</p>
+
+<p>The log4cxx environment is fully configurable programmatically.
+However, it is far more flexible to configure log4cxx using
+configuration files.  Currently, configuration files can be written in
+XML or in Java properties (key=value) format.</p>
+
+<p>Let us give a taste of how this is done with the help of an
+imaginary application <tt>MyApp</tt> that uses log4cxx.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCCCCC"><tr class="a"><td>
+<div><pre>
+#include &quot;com/foo/bar.h&quot;
+using namespace com::foo;
+
+// include log4cxx header files.
+#include &quot;log4cxx/logger.h&quot;
+#include &quot;log4cxx/basicconfigurator.h&quot;
+#include &quot;log4cxx/helpers/exception.h&quot;
+
+using namespace log4cxx;
+using namespace log4cxx::helpers;
+
+LoggerPtr logger(Logger::getLogger(&quot;MyApp&quot;));
+
+int main(int argc, char **argv)
+{
+        int result = EXIT_SUCCESS;
+        try
+        {
+                // Set up a simple configuration that logs on the console.
+                BasicConfigurator::configure();
+
+                LOG4CXX_INFO(logger, &quot;Entering application.&quot;)
+                Bar bar;
+                bar.doIt();
+                LOG4CXX_INFO(logger, &quot;Exiting application.&quot;)
+        }
+        catch(Exception&amp;)
+        {
+                result = EXIT_FAILURE;
+        }
+
+        return result;
+}
+</pre></div>
+</td></tr>
+</table>
+
+<p><tt>MyApp</tt> begins by including log4cxx headers.  It
+then defines a static logger variable with the name
+<tt>MyApp</tt> which happens to be the fully qualified name of the
+class.</p>
+
+<p><tt>MyApp</tt> uses the <tt>Bar</tt> class defined in header
+file <tt>com/foo/bar.h</tt>.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCCCCC"><tr class="a"><td>
+<div><pre>
+//  file com/foo/bar.h
+#include &quot;log4cxx/logger.h&quot;
+
+namespace com {
+   namespace foo {
+      class Bar {
+          static log4cxx::LoggerPtr logger;
+          
+      public:
+          void doIt();
+       }
+    }
+}
+</pre></div>
+
+<div><pre>
+// file bar.cpp
+#include &quot;com/foo/bar.h&quot;
+
+using namespace com::foo;
+using namespace log4cxx;
+
+LoggerPtr Bar::logger(Logger::getLogger(&quot;com.foo.bar&quot;));
+
+void Bar::doIt() {
+   LOG4CXX_DEBUG(logger, &quot;Did it again!&quot;)
+}
+</pre></div>
+</td></tr>
+</table>
+
+<p>The invocation of the <a href="apidocs/classlog4cxx_1_1BasicConfigurator.html#e0">BasicConfigurator::configure</a>
+method creates a rather simple log4cxx setup. This method is hardwired
+to add to the root logger a <a href="apidocs/classlog4cxx_1_1ConsoleAppender.html">
+ConsoleAppender</a>. The output will be formatted using a <a href="apidocs/classlog4cxx_1_1PatternLayout.html">PatternLayout</a> set
+to the pattern &quot;%-4r [%t] %-5p %c %x - %m%n&quot;.</p>
+
+<p>Note that by default, the root logger is assigned to
+<tt>Level::getDebug()</tt>.</p>
+
+<p>The output of MyApp is:
+</p><div><pre>
+0    [12345] INFO  MyApp  - Entering application.
+36   [12345] DEBUG com.foo.Bar  - Did it again!
+51   [12345] INFO  MyApp  - Exiting application.
+</pre></div>
+
+<p>The previous example always outputs the same log information.
+Fortunately, it is easy to modify <tt>MyApp</tt> so that the log
+output can be controlled at run-time. Here is a slightly modified
+version.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCCCCC"><tr class="a"><td>
+<div><pre>
+// file MyApp2.cpp
+
+#include &quot;com/foo/bar.h&quot;
+using namespace com::foo;
+
+// include log4cxx header files.
+#include &quot;log4cxx/logger.h&quot;
+#include &quot;log4cxx/basicconfigurator.h&quot;
+#include &quot;log4cxx/propertyconfigurator.h&quot;
+#include &quot;log4cxx/helpers/exception.h&quot;
+
+using namespace log4cxx;
+using namespace log4cxx::helpers;
+// Define a static logger variable so that it references the
+// Logger instance named &quot;MyApp&quot;.
+LoggerPtr logger(Logger::getLogger(&quot;MyApp&quot;));
+
+int main(int argc, char **argv)
+{
+        int result = EXIT_SUCCESS;
+        try
+        {
+                if (argc &gt; 1)
+                {
+                        // BasicConfigurator replaced with PropertyConfigurator.
+                        PropertyConfigurator::configure(argv[1]);
+                }
+                else
+                {
+                        BasicConfigurator::configure();
+                }
+
+                LOG4CXX_INFO(logger, &quot;Entering application.&quot;)
+                Bar bar
+                bar.doIt();
+                LOG4CXX_INFO(logger, &quot;Exiting application.&quot;)
+        }
+        catch(Exception&amp;)
+        {
+                result = EXIT_FAILURE;
+        }
+
+        return result;
+}
+</pre></div>
+</td></tr>
+</table>
+
+<p>This version of <tt>MyApp</tt> instructs
+<tt>PropertyConfigurator</tt> to parse a configuration file and
+set up logging accordingly.</p>
+
+<p>Here is a sample configuration file that results in exactly same
+output as the previous <tt>BasicConfigurator</tt> based example.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCAAAA"><tr class="a"><td>
+<div><pre>
+# Set root logger level to DEBUG and its only appender to A1.
+log4j.rootLogger=DEBUG, A1
+
+# A1 is set to be a ConsoleAppender.
+log4j.appender.A1=org.apache.log4j.ConsoleAppender
+
+# A1 uses PatternLayout.
+log4j.appender.A1.layout=org.apache.log4j.PatternLayout
+log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
+</pre></div>
+</td></tr></table>
+
+<p>It can be noticed that the PropertyConfigurator file format is the same as log4j.</p>
+
+<p>Suppose we are no longer interested in seeing the output of any
+component belonging to the <tt>com::foo</tt> package. The following
+configuration file shows one possible way of achieving this.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCAAAA"><tr class="a"><td>
+<div><pre>
+log4j.rootLogger=DEBUG, A1
+log4j.appender.A1=org.apache.log4j.ConsoleAppender
+log4j.appender.A1.layout=org.apache.log4j.PatternLayout
+
+# <b>Print the date in ISO 8601 format</b>
+log4j.appender.A1.layout.ConversionPattern=<b>%d</b> [%t] %-5p %c - %m%n
+
+# Print only messages of level WARN or above in the package com.foo.
+<b>log4j.logger.com.foo=WARN</b>
+</pre></div>
+</td></tr></table>
+
+<p>The output of <tt>MyApp</tt> configured with this file is shown below.</p>
+
+<div><pre>
+<b>2000-09-07 14:07:41,508</b> [12345] INFO  MyApp - Entering application.
+<b>2000-09-07 14:07:41,529</b> [12345] INFO  MyApp - Exiting application.
+</pre></div>
+
+<p>As the logger <tt>com.foo.Bar</tt> does not have an assigned
+level, it inherits its level from <tt>com.foo</tt>, which
+was set to WARN in the configuration file. The log statement from the
+<tt>Bar::doIt</tt> method has the level DEBUG, lower than the
+logger level WARN. Consequently, <tt>doIt()</tt> method's log
+request is suppressed.</p>
+
+<p>Here is another configuration file that uses multiple appenders.</p>
+
+<p></p><table border="0" class="bodyTable" bgcolor="CCAAAA"><tr class="a"><td>
+<div><pre>
+log4j.rootLogger=debug, <b>stdout, R</b>
+
+log4j.appender.<b>stdout</b>=org.apache.log4j.ConsoleAppender
+log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
+
+# Pattern to output the caller's file name and line number.
+log4j.appender.stdout.layout.ConversionPattern=%5p [%t] <b>(%F:%L)</b> - %m%n
+
+log4j.appender.<b>R</b>=org.apache.log4j.RollingFileAppender
+log4j.appender.R.File=example.log
+
+log4j.appender.R.MaxFileSize=<b>100KB</b>
+# Keep one backup file
+log4j.appender.R.MaxBackupIndex=1
+
+log4j.appender.R.layout=org.apache.log4j.PatternLayout
+log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
+</pre></div>
+</td></tr></table>
+
+<p>Calling the enhanced MyApp with the this configuration file will
+output the following on the console.</p>
+
+<div><pre>
+ INFO [12345] <b>(MyApp2.cpp:31)</b> - Entering application.
+DEBUG [12345] (Bar.h:16) - Doing it again!
+ INFO [12345] (MyApp2.cpp:34) - Exiting application.
+</pre></div>
+
+<p>In addition, as the root logger has been allocated a second
+appender, output will also be directed to the <tt>example.log</tt>
+file. This file will be rolled over when it reaches 100KB. When
+roll-over occurs, the old version of <tt>example.log</tt> is
+automatically moved to <tt>example.log.1</tt>.</p>
+
+<p>Note that to obtain these different logging behaviors we did not
+need to recompile code. We could just as easily have logged to a UNIX
+Syslog daemon, redirected all <tt>com.foo</tt> output to an NT
+Event logger, or forwarded logging events to a remote log4cxx server,
+which would log according to local server policy, for example by
+forwarding the log event to a second log4cxx server.</p>
+
+<a name="defaultInit"></a><div class="section"><h2>Default Initialization Procedure<a name="Default_Initialization_Procedure"></a></h2>
+
+<p>The log4cxx library does not make any assumptions about its
+environment. In particular, there are no default log4cxx
+appenders. Under certain well-defined circumstances however, the
+static inializer of the <tt>Logger</tt> class will attempt to
+automatically configure log4cxx.</p>
+
+<p>The exact default initialization algorithm is defined as follows:</p>
+
+<ol style="list-style-type: decimal">
+
+  <li><p>Set the configurationOptionStr string variable to the value of the 
+  <b>LOG4CXX_CONFIGURATION</b> environment variable if set, otherwise 
+  the value of the <b>log4j.configuration</b> or <b>LOG4CXX_CONFIGURATION</b>
+  environment variable if set, 
+  otherwise the first of the following file names which exist in the 
+  current working directory, &quot;log4cxx.xml&quot;, &quot;log4cxx.properties&quot;, 
+  &quot;log4j.xml&quot; and &quot;log4j.properties&quot;. 
+  If configurationOptionStr has not been set, then disable logging.</p></li> 
+
+  <li><p>Unless a custom configurator is specified using the 
+  <b>LOG4CXX_CONFIGURATOR_CLASS</b> or <b>log4j.configuratorClass</b>
+  environment variable, the PropertyConfigurator will be used to configure
+  log4cxx unless the file name ends with the &quot;.xml&quot; extension, 
+  in which case the DOMConfigurator will be used. 
+  If a custom configurator is specified, the environment variable 
+  should contain a fully qualified class name of a class that 
+  implements the Configurator interface.</p>
+  </li>
+
+</ol>
+
+
+<div class="section"><h2> Nested Diagnostic Contexts<a name="Nested_Diagnostic_Contexts"></a></h2>
+
+<p>Most real-world systems have to deal with multiple clients
+simultaneously. In a typical multithreaded implementation of such a
+system, different threads will handle different clients. Logging is
+especially well suited to trace and debug complex distributed
+applications. A common approach to differentiate the logging output of
+one client from another is to instantiate a new separate logger for
+each client. This promotes the proliferation of loggers and
+increases the management overhead of logging.</p>
+
+<p>A lighter technique is to uniquely stamp each log request initiated
+from the same client interaction. Neil Harrison described this method
+in the book &quot;Patterns for Logging Diagnostic Messages,&quot; in <i>Pattern
+Languages of Program Design 3</i>, edited by R. Martin, D.  Riehle,
+and F. Buschmann (Addison-Wesley, 1997).</p>
+
+
+
+<p> To uniquely stamp each request, the
+user pushes contextual information into the NDC, the abbreviation of
+<i>Nested Diagnostic Context</i>. The NDC class is shown below.
+
+</p><div><pre>
+namespace log4cxx {
+  class NDC {
+  public:
+    //  pushes the value on construction and pops on destruction.
+    NDC(const std::string&amp; value);
+    NDC(const std::wstring&amp; value);
+
+    // Remove the top of the context from the NDC.
+    <b>static</b> LogString pop();
+
+    // Add diagnostic context for the current thread.
+    <b>static</b> void push(const std::string&amp; message);
+    <b>static</b> void push(const std::wstring&amp; message);
+  }
+</pre></div>
+
+<p>The NDC is managed per thread as a <i>stack</i> of contextual
+information. Note that all methods of the <tt>log4cxx::NDC</tt>
+class are static. Assuming that NDC printing is turned on, every time
+a log request is made, the appropriate log4cxx component will include
+the <i>entire</i> NDC stack for the current thread in the log
+output. This is done without the intervention of the user, who is
+responsible only for placing the correct information in the NDC by
+using the <tt>push</tt> and <tt>pop</tt> methods at a few
+well-defined points in the code.  In contrast, the per-client logger
+approach commands extensive changes in the code.</p>
+
+<p>To illustrate this point, let us take the example of a servlet
+delivering content to numerous clients. The servlet can build the NDC
+at the very beginning of the request before executing other code. The
+contextual information can be the client's host name and other
+information inherent to the request, typically information contained
+in cookies. Hence, even if the servlet is serving multiple clients
+simultaneously, the logs initiated by the same code, i.e. belonging to
+the same logger, can still be distinguished because each client
+request will have a different NDC stack. Contrast this with the
+complexity of passing a freshly instantiated logger to all code
+exercised during the client's request.</p>
+
+<p>Nevertheless, some sophisticated applications, such as virtual
+hosting web servers, must log differently depending on the virtual
+host context and also depending on the software component issuing the
+request. Recent log4cxx releases support multiple hierarchy trees. This
+enhancement allows each virtual host to possess its own copy of the
+logger hierarchy.</p>
+
+
+<a name="performance"></a><div class="section"><h2>Performance<a name="Performance"></a></h2>
+
+<p>One of the often-cited arguments against logging is its
+computational cost. This is a legitimate concern as even moderately
+sized applications can generate thousands of log requests.  Much
+effort was spent measuring and tweaking logging performance. Log4cxx
+claims to be fast and flexible: speed first, flexibility second.</p>
+
+<p>The user should be aware of the following performance issues.</p>
+
+<ol style="list-style-type: decimal">
+  <li><b>Logging performance when logging is turned off.</b><br />
+
+   <p>When logging is turned
+   off entirely or just for a set
+   of levels, the cost of a log request consists of a method
+   invocation plus an integer comparison.  The LOG4CXX_DEBUG and similar
+   macros suppress unnecessary expression evaluation if the
+   request is not enabled.</p></li>
+
+   <li><b>The performance of deciding whether to log or not to log when
+       logging is turned on.</b><br />
+
+   <p>This is essentially the performance of walking the logger
+   hierarchy. When logging is turned on, log4cxx still needs to compare
+       the level of the log request with the level of the request
+   logger. However, loggers may not have an assigned
+   level; they can inherit them from the logger hierarchy. Thus,
+   before inheriting a level, the logger may need to search its
+   ancestors.</p>
+
+   <p>There has been a serious effort to make this hierarchy walk to
+be as fast as possible. For example, child loggers link only to
+their existing ancestors. In the <tt>BasicConfigurator</tt>
+example shown earlier, the logger named <tt>com.foo.Bar</tt> is
+linked directly to the root logger, thereby circumventing the
+nonexistent <tt>com</tt> or <tt>com.foo</tt> loggers. This
+significantly improves the speed of the walk, especially in &quot;sparse&quot;
+hierarchies.</p>
+
+       <p>The cost of walking the hierarchy is typically 3
+       times slower than when logging is turned off entirely.</p></li>
+
+   <li><b>Actually outputting log messages</b><br />
+
+   <p>This is the cost of formatting the log output and sending it to
+   its target destination. Here again, a serious effort was made to
+   make layouts (formatters) perform as quickly as possible. The same
+   is true for appenders.</p>
+
+   </li>
+
+</ol>
+
+
+<div class="section"><h2>Conclusions<a name="Conclusions"></a></h2>
+
+<p>Apache Log4cxx is a popular logging package written in C++.  One of its
+distinctive features is the notion of inheritance in loggers. Using
+a logger hierarchy it is possible to control which log statements
+are output at arbitrary granularity. This helps reduce the volume of
+logged output and minimize the cost of logging.</p>
+
+<p>One of the advantages of the log4cxx API is its manageability. Once
+the log statements have been inserted into the code, they can be
+controlled with configuration files. They can be selectively enabled
+or disabled, and sent to different and multiple output targets in
+user-chosen formats. The log4cxx package is designed so that log
+statements can remain in shipped code without incurring a heavy
+performance cost.</p>
+
+</div>
+
+
+      </div>
+    </div>
+    <div class="clear">
+      <hr/>
+    </div>
+    <div id="footer">
+      <div class="xleft">Copyright &#169;                    2012
+                        <a href="http://www.apache.org">Apache Software Foundation</a>.
+                  
+        
+       Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache Software License, Version 2.0</a>.</div>
+      <div class="xleft">Apache log4cxx, Apache, the Apache feather logo,
+   the Apache Logging Services project logo and the Built by Maven logo are trademarks of The Apache Software Foundation.</div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+  </body>
+</html>

Propchange: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/issue-tracking.html
==============================================================================
--- websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/issue-tracking.html (added)
+++ websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/issue-tracking.html Wed Jun 20 09:25:02 2012
@@ -0,0 +1,170 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+-->
+<!-- Generated by Apache Maven Doxia at Jun 20, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+    <title>Issue Tracking</title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <meta name="Date-Revision-yyyymmdd" content="20120620" />
+    <meta http-equiv="Content-Language" content="en" />
+      </head>
+  <body class="composite">
+    <div id="banner">
+                  <a href="http://logging.apache.org/" id="bannerLeft">
+                                                <img src="images/ls-logo.jpg" alt="Logging Services" />
+                </a>
+                    <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="breadcrumbs">
+            
+        
+                <div class="xleft">
+        <span id="publishDate">Last Published: 2012-06-20</span>
+                  &nbsp;| <span id="projectVersion">Version: 0.11.0-SNAPSHOT</span>
+                          |                           <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+                &gt;
+                              <a href="http://logging.apache.org/" class="externalLink" title="Logging Services">Logging Services</a>
+                &gt;
+                              <a href="./" title="log4cxx">log4cxx</a>
+                          </div>
+            <div class="xright">        
+        
+      </div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="leftColumn">
+      <div id="navcolumn">
+             
+        
+                                <h5>Get Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="download.html" title="Download">Download</a>
+            </li>
+                  <li class="none">
+                          <a href="changes-report.html" title="Changes">Changes</a>
+            </li>
+                  <li class="none">
+                          <a href="license.html" title="License">License</a>
+            </li>
+          </ul>
+                       <h5>About Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="index.html" title="What is log4cxx?">What is log4cxx?</a>
+            </li>
+                  <li class="none">
+                          <a href="apidocs/index.html" title="API Documentation">API Documentation</a>
+            </li>
+                  <li class="none">
+                          <a href="faq.html" title="FAQ">FAQ</a>
+            </li>
+          </ul>
+                       <h5>Community</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+            </li>
+                  <li class="none">
+            <strong>Issue Tracking</strong>
+          </li>
+                  <li class="none">
+                          <a href="http://wiki.apache.org/logging-log4cxx" class="externalLink" title="Wiki">Wiki</a>
+            </li>
+          </ul>
+                       <h5>Development</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="source-repository.html" title="Repository">Repository</a>
+            </li>
+                                                                                                                                      <li class="expanded">
+                          <a href="#" title="Building">Building</a>
+                    <ul>
+                      <li class="none">
+                          <a href="building/autotools.html" title="autotools">autotools</a>
+            </li>
+                      <li class="none">
+                          <a href="building/ant.html" title="Apache Ant">Apache Ant</a>
+            </li>
+                      <li class="none">
+                          <a href="building/maven.html" title="Apache Maven 2">Apache Maven 2</a>
+            </li>
+                      <li class="none">
+                          <a href="building/vstudio.html" title="Microsoft Visual Studio">Microsoft Visual Studio</a>
+            </li>
+                      <li class="none">
+                          <a href="building/xcode.html" title="Apple Xcode">Apple Xcode</a>
+            </li>
+              </ul>
+        </li>
+          </ul>
+                       <h5>Apache</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="http://www.apache.org" class="externalLink" title="Home">Home</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsorship">Sponsorship</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apachecon.com" class="externalLink" title="Conferences">Conferences</a>
+            </li>
+          </ul>
+                             <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+        <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+      </a>
+                   
+        
+            </div>
+    </div>
+    <div id="bodyColumn">
+      <div id="contentBox">
+        <div class="section"><h2>Overview<a name="Overview"></a></h2><a name="Overview"></a><p>This project uses <a class="externalLink" href="http://www.atlassian.com/software/jira">JIRA</a> a J2EE-based, issue tracking and project management application.</p></div><div class="section"><h2>Issue Tracking<a name="Issue_Tracking"></a></h2><a name="Issue_Tracking"></a><p>Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.</p><div class="source"><pre><a class="externalLink" href="http://issues.apache.org/jira/">http://issues.apache.org/jira/</a></pre></div></div>
+      </div>
+    </div>
+    <div class="clear">
+      <hr/>
+    </div>
+    <div id="footer">
+      <div class="xleft">Copyright &#169;                    2012
+                        <a href="http://www.apache.org">Apache Software Foundation</a>.
+                  
+        
+       Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache Software License, Version 2.0</a>.</div>
+      <div class="xleft">Apache log4cxx, Apache, the Apache feather logo,
+   the Apache Logging Services project logo and the Built by Maven logo are trademarks of The Apache Software Foundation.</div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+  </body>
+</html>

Propchange: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/issue-tracking.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/license.html
==============================================================================
--- websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/license.html (added)
+++ websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/license.html Wed Jun 20 09:25:02 2012
@@ -0,0 +1,372 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+-->
+<!-- Generated by Apache Maven Doxia at Jun 20, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+    <title>Project License</title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <meta name="Date-Revision-yyyymmdd" content="20120620" />
+    <meta http-equiv="Content-Language" content="en" />
+      </head>
+  <body class="composite">
+    <div id="banner">
+                  <a href="http://logging.apache.org/" id="bannerLeft">
+                                                <img src="images/ls-logo.jpg" alt="Logging Services" />
+                </a>
+                    <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="breadcrumbs">
+            
+        
+                <div class="xleft">
+        <span id="publishDate">Last Published: 2012-06-20</span>
+                  &nbsp;| <span id="projectVersion">Version: 0.11.0-SNAPSHOT</span>
+                          |                           <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+                &gt;
+                              <a href="http://logging.apache.org/" class="externalLink" title="Logging Services">Logging Services</a>
+                &gt;
+                              <a href="./" title="log4cxx">log4cxx</a>
+                          </div>
+            <div class="xright">        
+        
+      </div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="leftColumn">
+      <div id="navcolumn">
+             
+        
+                                <h5>Get Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="download.html" title="Download">Download</a>
+            </li>
+                  <li class="none">
+                          <a href="changes-report.html" title="Changes">Changes</a>
+            </li>
+                  <li class="none">
+            <strong>License</strong>
+          </li>
+          </ul>
+                       <h5>About Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="index.html" title="What is log4cxx?">What is log4cxx?</a>
+            </li>
+                  <li class="none">
+                          <a href="apidocs/index.html" title="API Documentation">API Documentation</a>
+            </li>
+                  <li class="none">
+                          <a href="faq.html" title="FAQ">FAQ</a>
+            </li>
+          </ul>
+                       <h5>Community</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+            </li>
+                  <li class="none">
+                          <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+            </li>
+                  <li class="none">
+                          <a href="http://wiki.apache.org/logging-log4cxx" class="externalLink" title="Wiki">Wiki</a>
+            </li>
+          </ul>
+                       <h5>Development</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="source-repository.html" title="Repository">Repository</a>
+            </li>
+                                                                                                                                      <li class="expanded">
+                          <a href="#" title="Building">Building</a>
+                    <ul>
+                      <li class="none">
+                          <a href="building/autotools.html" title="autotools">autotools</a>
+            </li>
+                      <li class="none">
+                          <a href="building/ant.html" title="Apache Ant">Apache Ant</a>
+            </li>
+                      <li class="none">
+                          <a href="building/maven.html" title="Apache Maven 2">Apache Maven 2</a>
+            </li>
+                      <li class="none">
+                          <a href="building/vstudio.html" title="Microsoft Visual Studio">Microsoft Visual Studio</a>
+            </li>
+                      <li class="none">
+                          <a href="building/xcode.html" title="Apple Xcode">Apple Xcode</a>
+            </li>
+              </ul>
+        </li>
+          </ul>
+                       <h5>Apache</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="http://www.apache.org" class="externalLink" title="Home">Home</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsorship">Sponsorship</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apachecon.com" class="externalLink" title="Conferences">Conferences</a>
+            </li>
+          </ul>
+                             <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+        <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+      </a>
+                   
+        
+            </div>
+    </div>
+    <div id="bodyColumn">
+      <div id="contentBox">
+        <div class="section"><h2>Overview<a name="Overview"></a></h2><a name="Overview"></a><p>Typically the licenses listed for the project are that of the project itself, and not of dependencies.</p></div><div class="section"><h2>Project License<a name="Project_License"></a></h2><a name="Project_License"></a><div class="section"><h3>Apache License, Version 2.0<a name="Apache_License_Version_2.0"></a></h3><a name="Apache_License_Version_2.0"></a><div class="source"><pre>
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      &quot;License&quot; shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      &quot;Licensor&quot; shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      &quot;Legal Entity&quot; shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      &quot;control&quot; means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      &quot;You&quot; (or &quot;Your&quot;) shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      &quot;Source&quot; form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      &quot;Object&quot; form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      &quot;Work&quot; shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      &quot;Derivative Works&quot; shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      &quot;Contribution&quot; shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, &quot;submitted&quot;
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as &quot;Not a Contribution.&quot;
+
+      &quot;Contributor&quot; shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a &quot;NOTICE&quot; text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an &quot;AS IS&quot; BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets &quot;[]&quot;
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same &quot;printed page&quot; as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the &quot;License&quot;);
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an &quot;AS IS&quot; BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+</pre></div></div></div>
+      </div>
+    </div>
+    <div class="clear">
+      <hr/>
+    </div>
+    <div id="footer">
+      <div class="xleft">Copyright &#169;                    2012
+                        <a href="http://www.apache.org">Apache Software Foundation</a>.
+                  
+        
+       Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache Software License, Version 2.0</a>.</div>
+      <div class="xleft">Apache log4cxx, Apache, the Apache feather logo,
+   the Apache Logging Services project logo and the Built by Maven logo are trademarks of The Apache Software Foundation.</div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+  </body>
+</html>

Propchange: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/license.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/mail-lists.html
==============================================================================
--- websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/mail-lists.html (added)
+++ websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/mail-lists.html Wed Jun 20 09:25:02 2012
@@ -0,0 +1,170 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+-->
+<!-- Generated by Apache Maven Doxia at Jun 20, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+    <title>Project Mailing Lists</title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <meta name="Date-Revision-yyyymmdd" content="20120620" />
+    <meta http-equiv="Content-Language" content="en" />
+      </head>
+  <body class="composite">
+    <div id="banner">
+                  <a href="http://logging.apache.org/" id="bannerLeft">
+                                                <img src="images/ls-logo.jpg" alt="Logging Services" />
+                </a>
+                    <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="breadcrumbs">
+            
+        
+                <div class="xleft">
+        <span id="publishDate">Last Published: 2012-06-20</span>
+                  &nbsp;| <span id="projectVersion">Version: 0.11.0-SNAPSHOT</span>
+                          |                           <a href="http://www.apache.org/" class="externalLink" title="Apache">Apache</a>
+                &gt;
+                              <a href="http://logging.apache.org/" class="externalLink" title="Logging Services">Logging Services</a>
+                &gt;
+                              <a href="./" title="log4cxx">log4cxx</a>
+                          </div>
+            <div class="xright">        
+        
+      </div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+    <div id="leftColumn">
+      <div id="navcolumn">
+             
+        
+                                <h5>Get Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="download.html" title="Download">Download</a>
+            </li>
+                  <li class="none">
+                          <a href="changes-report.html" title="Changes">Changes</a>
+            </li>
+                  <li class="none">
+                          <a href="license.html" title="License">License</a>
+            </li>
+          </ul>
+                       <h5>About Apache log4cxx</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="index.html" title="What is log4cxx?">What is log4cxx?</a>
+            </li>
+                  <li class="none">
+                          <a href="apidocs/index.html" title="API Documentation">API Documentation</a>
+            </li>
+                  <li class="none">
+                          <a href="faq.html" title="FAQ">FAQ</a>
+            </li>
+          </ul>
+                       <h5>Community</h5>
+                  <ul>
+                  <li class="none">
+            <strong>Mailing Lists</strong>
+          </li>
+                  <li class="none">
+                          <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+            </li>
+                  <li class="none">
+                          <a href="http://wiki.apache.org/logging-log4cxx" class="externalLink" title="Wiki">Wiki</a>
+            </li>
+          </ul>
+                       <h5>Development</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="source-repository.html" title="Repository">Repository</a>
+            </li>
+                                                                                                                                      <li class="expanded">
+                          <a href="#" title="Building">Building</a>
+                    <ul>
+                      <li class="none">
+                          <a href="building/autotools.html" title="autotools">autotools</a>
+            </li>
+                      <li class="none">
+                          <a href="building/ant.html" title="Apache Ant">Apache Ant</a>
+            </li>
+                      <li class="none">
+                          <a href="building/maven.html" title="Apache Maven 2">Apache Maven 2</a>
+            </li>
+                      <li class="none">
+                          <a href="building/vstudio.html" title="Microsoft Visual Studio">Microsoft Visual Studio</a>
+            </li>
+                      <li class="none">
+                          <a href="building/xcode.html" title="Apple Xcode">Apple Xcode</a>
+            </li>
+              </ul>
+        </li>
+          </ul>
+                       <h5>Apache</h5>
+                  <ul>
+                  <li class="none">
+                          <a href="http://www.apache.org" class="externalLink" title="Home">Home</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/sponsorship.html" class="externalLink" title="Sponsorship">Sponsorship</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apache.org/foundation/thanks.html" class="externalLink" title="Thanks">Thanks</a>
+            </li>
+                  <li class="none">
+                          <a href="http://www.apachecon.com" class="externalLink" title="Conferences">Conferences</a>
+            </li>
+          </ul>
+                             <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+        <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+      </a>
+                   
+        
+            </div>
+    </div>
+    <div id="bodyColumn">
+      <div id="contentBox">
+        <div class="section"><h2>Project Mailing Lists<a name="Project_Mailing_Lists"></a></h2><a name="Project_Mailing_Lists"></a><p>These are the mailing lists that have been established for this project. For each list, there is a subscribe, unsubscribe, and an archive link.</p><table border="0" class="bodyTable"><tr class="a"><th>Name</th><th>Subscribe</th><th>Unsubscribe</th><th>Post</th><th>Archive</th><th>Other Archives</th></tr><tr class="b"><td>log4cxx-user : log4cxx usage</td><td><a class="externalLink" href="mailto:log4cxx-user-subscribe@logging.apache.org">Subscribe</a></td><td><a class="externalLink" href="mailto:log4cxx-user-unsubscribe@logging.apache.org">Unsubscribe</a></td><td><a class="externalLink" href="mailto:log4cxx-user@logging.apache.org">Post</a></td><td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/logging-log4cxx-user/">mail-archives.apache.org</a></td><td><a class="externalLink" href="http://markmail.org/search/list:org.apa
 che.logging.log4cxx-user">markmail.org</a></td></tr><tr class="a"><td>-</td><td>-</td><td>-</td><td>-</td><td>-</td><td><a class="externalLink" href="http://marc.info/?l=log4cxx-user">marc.info</a></td></tr><tr class="b"><td>-</td><td>-</td><td>-</td><td>-</td><td>-</td><td><a class="externalLink" href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.user">dir.gmane.org</a></td></tr><tr class="a"><td>log4cxx-dev : log4cxx development</td><td><a class="externalLink" href="mailto:log4cxx-dev-subscribe@logging.apache.org">Subscribe</a></td><td><a class="externalLink" href="mailto:log4cxx-dev-unsubscribe@logging.apache.org">Unsubscribe</a></td><td><a class="externalLink" href="mailto:log4cxx-dev@logging.apache.org">Post</a></td><td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/">mail-archives.apache.org</a></td><td><a class="externalLink" href="http://markmail.org/search/list:org.apache.logging.log4cxx-dev">markmail.org</a></td
 ></tr><tr class="b"><td>-</td><td>-</td><td>-</td><td>-</td><td>-</td><td><a class="externalLink" href="http://marc.info/?l=log4cxx-dev">marc.info</a></td></tr><tr class="a"><td>-</td><td>-</td><td>-</td><td>-</td><td>-</td><td><a class="externalLink" href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.devel">dir.gmane.org</a></td></tr></table></div>
+      </div>
+    </div>
+    <div class="clear">
+      <hr/>
+    </div>
+    <div id="footer">
+      <div class="xleft">Copyright &#169;                    2012
+                        <a href="http://www.apache.org">Apache Software Foundation</a>.
+                  
+        
+       Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache Software License, Version 2.0</a>.</div>
+      <div class="xleft">Apache log4cxx, Apache, the Apache feather logo,
+   the Apache Logging Services project logo and the Built by Maven logo are trademarks of The Apache Software Foundation.</div>
+      <div class="clear">
+        <hr/>
+      </div>
+    </div>
+  </body>
+</html>

Propchange: websites/production/loggingtest/content/log4cxx/log4cxx-0.11.0-SNAPSHOT/mail-lists.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message