logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwom...@apache.org
Subject cvs commit: logging-log4j/src/xdocs/stylesheets project.xml
Date Fri, 06 May 2005 05:32:36 GMT
mwomack     2005/05/05 22:32:36

  Modified:    .        Tag: v1_2-branch build.xml
               docs     Tag: v1_2-branch FAQ.html HISTORY.txt
               src/java/org/apache/log4j Tag: v1_2-branch Category.java
                        Logger.java
               src/xdocs Tag: v1_2-branch contactUs.xml contributors.xml
                        documentation.xml download.xml earlier.xml
                        history.xml index.xml plan.xml
               src/xdocs/stylesheets Tag: v1_2-branch project.xml
  Removed:     .        Tag: v1_2-branch slf4j.xml
               src/filtered-java/org/slf4j Tag: v1_2-branch
                        LoggerFactory.java LoggerFactoryAdapter.java
                        ULogger.java
               src/filtered-java/org/slf4j/impl Tag: v1_2-branch
                        JDK14Logger.java JDK14LoggerFA.java
                        MessageFormatter.java NOPLogger.java
                        NOPLoggerFA.java SimpleLogger.java
                        SimpleLoggerFA.java
               src/java/org/slf4j/impl Tag: v1_2-branch Log4jLoggerFA.java
                        MessageFormatter.java NOPLogger.java
                        NOPLoggerFA.java SimpleLogger.java
                        SimpleLoggerFA.java
  Log:
  Reverted to v1.2.9 version of files to remove slf4j changes and references.
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.34.2.16 +4 -27     logging-log4j/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/build.xml,v
  retrieving revision 1.34.2.15
  retrieving revision 1.34.2.16
  diff -u -r1.34.2.15 -r1.34.2.16
  --- build.xml	29 Apr 2005 17:39:41 -0000	1.34.2.15
  +++ build.xml	6 May 2005 05:32:35 -0000	1.34.2.16
  @@ -17,7 +17,7 @@
     <!-- prefixed with "env". -->
     <property environment="env"/>
   
  -  <property name="version" value="1.2.10"/>
  +  <property name="version" value="1.2.11prerelease"/>
   
     <!-- The base directory relative to which most targets are built -->
     <property name="base" value="."/>
  @@ -161,19 +161,6 @@
       <echo message="JAVAMAIL is present."/>
     </target>
   
  -  <target name="slf4jCheck">
  -    <available file="${java.source.dir}/org/slf4j/ULogger.java"
  -               property="slf4j-present"/>
  -    
  -    <fail unless="slf4j-present">
  -       Missing src/java/org/slf4j/*.java source files.
  -  	  		
  -       Just run the refresh-slf4j target with the command:
  -
  -       ant refresh-slf4j		
  -    </fail>
  -  </target>
  -
     <!-- ================================================================= -->
     <!-- Initialize variables                                              -->
     <!-- NOTE: all directories are relative to jakarta-log4j/              -->
  @@ -182,22 +169,14 @@
       <tstamp />
     </target>
   
  -
  -  <target name="refresh-slf4j">
  -    <echo>Fecthing required source files from SLF4J.ORG</echo> 
  -    <!-- copy required SLF4J files into log4j -->
  -    <ant antfile="slf4j.xml" target="refresh-slf4j"/>
  -  </target>
  -
     <target name="build" depends="init, build.core, build.examples, build.xml,
                                   build.javamail, build.jms, build.jmx"/>
   
  -  <target name="build.core" depends="init, slf4jCheck">
  +  <target name="build.core" depends="init">
       <mkdir dir="${javac.dest}" />
       <javac srcdir="${java.source.dir}"
   	   destdir="${javac.dest}"
  -	   includes="org/slf4j/**/*.java,
  -                     ${stem}/**/*.java, 
  +	   includes="${stem}/**/*.java, 
                        ${stem}/xml/XMLLayout.java"
   	   excludes="misc/*, **/UnitTest*.java,
                       **/StressCategory.java,
  @@ -347,8 +326,7 @@
       </delete>
   
       <jar jarfile="${jar.dest}/${jar.filename}" basedir="${javac.dest}"
  -      includes="org/slf4j/**/*.class,
  -                ${stem}/*.class, 
  +      includes="${stem}/*.class, 
                   ${stem}/xml/log4j.dtd,
                   ${stem}/config/*.class,
   	        ${stem}/helpers/*.class,
  @@ -411,7 +389,6 @@
   
         <link href="http://java.sun.com/products/jdk/1.3/docs/api/"/>
         <link href="http://java.sun.com/j2ee/sdk_1.3/techdocs/api/"/>
  -      <link href="http://www.slf4j.org/api/"/>
         <classpath refid="compile.classpath"/>
       </javadoc>
     </target>
  
  
  
  No                   revision
  No                   revision
  1.15.2.5  +5 -42     logging-log4j/docs/Attic/FAQ.html
  
  Index: FAQ.html
  ===================================================================
  RCS file: /home/cvs/logging-log4j/docs/Attic/FAQ.html,v
  retrieving revision 1.15.2.4
  retrieving revision 1.15.2.5
  diff -u -r1.15.2.4 -r1.15.2.5
  --- FAQ.html	29 Apr 2005 17:39:41 -0000	1.15.2.4
  +++ FAQ.html	6 May 2005 05:32:35 -0000	1.15.2.5
  @@ -346,8 +346,9 @@
   	  remote Unix Syslog daemon, to a remote listener using JMS,
   	  to the NT EventLog or even send e-mail.  </p></li>
   
  -	  <li><p>log4j uses 6 levels, namely TRACE, DEBUG, INFO, WARN,
  -	  ERROR and FATAL.  </p></li>
  +	  <li><p>log4j uses 5 levels, namely DEBUG, INFO, WARN, ERROR and
  +	  FATAL.
  +	  </p></li>
   
   	  <li><p>The format of the log output can be easily changed by
   	  extending the <code>Layout</code>
  @@ -444,7 +445,7 @@
   
           <p>The open and collaborative way in which log4j is developped
           ensures that it continues to preserve and even widen its
  -        competitive edge. At some point, input from bright developpers
  +        competitive edge. At some point, input from bright developers
           from all over the world is bound to make a difference.
           </p>
         
  @@ -535,44 +536,6 @@
   	statement.
   	</p>
   	
  -        <h3>Better alternative based on message patterns</h3>
  -        <p>As of log4j version 1.3, there exists a significantly more
  -        convenient alternative based on message patterns. Assuming
  -        <code>entry</code> is an object, you can write:
  -        </p>
  -
  -	<p class="source">
  -          l.debug("The new entry is {}.", entry);
  -	</p>
  -
  -        <p>After evaluting whether to log or not, and only if the
  -        decision is positive, will the logger instace format the
  -        message and replace the '{}' pair with the string value of
  -        <code>entry</code>. In other words, the paramerized form does
  -        not incur the cost of parameter construction in case the log
  -        statement is disabled.
  -        </p>
  -        
  -        <p>Thus, the following two lines will yield the exact same
  -        output. However, the second form will perform at least 30
  -        (thirty) times faster in case of a <em>disabled</em> logging
  -        statement.
  -        </p>
  -        
  -	<p class="source">
  -          l.debug("The new entry is "+entry+"."); <br />
  -          l.debug("The new entry is {}.", entry);
  -	</p>
  -        
  -        <p>A two argument variant is also availalble. For example, you
  -        can write:
  -        </p>
  -	<p class="source">
  -          l.debug("The new entry is {}. It replaces {}.", entry, oldEntry);
  -	</p>
  -        
  -     
  -
         
                                    <div class="question">
                <a name="2.4">2.4  Are there any suggested ways for naming loggers?</a>
  @@ -1079,7 +1042,7 @@
   	appear in the file <em>/docs/faq.html</em>.
   	</p>
         
  -                                                                
  +                    
   
                
                   <!-- FOOTER -->
  
  
  
  1.27.2.2  +8 -12     logging-log4j/docs/HISTORY.txt
  
  Index: HISTORY.txt
  ===================================================================
  RCS file: /home/cvs/logging-log4j/docs/HISTORY.txt,v
  retrieving revision 1.27.2.1
  retrieving revision 1.27.2.2
  diff -u -r1.27.2.1 -r1.27.2.2
  --- HISTORY.txt	29 Apr 2005 17:07:43 -0000	1.27.2.1
  +++ HISTORY.txt	6 May 2005 05:32:35 -0000	1.27.2.2
  @@ -5,23 +5,19 @@
          client code. 
    [***] Changes requiring important modifications to existing client code.
   
  + Current cvs v1_2-branch (1.2.11 prerelease)
   
  + - Fixed bug #34491 whereby the class o.a.log4j.or.jms.MessageRenderer
  +   would not be compiled in the build.jms target. Bug reported by Andy
  +   McBride. http://issues.apache.org/bugzilla/show_bug.cgi?id=34491
  + 
    April 28th, 2005
   
    - Release of version 1.2.10
   
  - - Added support for the SLF4J project. The Logger class now
  -   implements the ULogger interface defined by the SLF4J. See
  -   
  -    http://www.slf4j.org
  -   
  -   for more detailed information.
  -
  - - Fixed bug #34491 whereby the class o.a.log4j.or.jms.MessageRenderer
  -   would not be compiled in the build.jms target. Bug reported by Andy
  -   McBride.
  -  
  - http://issues.apache.org/bugzilla/show_bug.cgi?id=34491
  + - Version 1.2.10 was not following the accepted rules and process of the
  +   log4j project and Logging Services Project and was recalled and removed.
  +   Please do not use version 1.2.10.
   
    November 1st, 2004
   
  
  
  
  No                   revision
  No                   revision
  1.68.2.7  +0 -246    logging-log4j/src/java/org/apache/log4j/Category.java
  
  Index: Category.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/Category.java,v
  retrieving revision 1.68.2.6
  retrieving revision 1.68.2.7
  diff -u -r1.68.2.6 -r1.68.2.7
  --- Category.java	28 Apr 2005 20:34:04 -0000	1.68.2.6
  +++ Category.java	6 May 2005 05:32:36 -0000	1.68.2.7
  @@ -31,7 +31,6 @@
   import java.util.MissingResourceException;
   import java.util.ResourceBundle;
   
  -import org.slf4j.impl.MessageFormatter;
   
   /**
     * <font color="#AA2222"><b>This class has been deprecated and
  @@ -250,60 +249,6 @@
       }
     }
   
  -  /**
  -   * Log a message with the <code>DEBUG</code> level with message formatting
  -   * done according to the value of <code>messagePattern</code> and 
  -   * <code>arg</code> parameters.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   * 
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg The argument to replace the formatting element, i,e, 
  -   * the '{}' pair within <code>messagePattern</code>.
  -   * @since 1.2.10
  -   */
  -  public void debug(Object messagePattern, Object arg) {
  -    if (repository.isDisabled(Level.DEBUG_INT)) {
  -      return;
  -    }
  -    
  -    if (Level.DEBUG.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      if (messagePattern instanceof String){
  -        String msgStr = (String) messagePattern;
  -        msgStr = MessageFormatter.format(msgStr, arg);
  -        forcedLog(FQCN, Level.DEBUG, msgStr, null);
  -      } else {
  -        // To be failsafe, we handle the case where 'messagePattern' is not
  -        // a String. Unless the user makes a mistake, this should never happen.
  -        forcedLog(FQCN, Level.DEBUG, messagePattern, null);
  -      }
  -    }
  -  }
  -
  -  /**
  -   * Log a message with the <code>DEBUG</code> level with message formatting
  -   * done according to the messagePattern and the arguments arg1 and arg2.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   * 
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg1 The first argument to replace the first formatting element
  -   * @param arg2 The second argument to replace the second formatting element
  -   * @since 1.2.10
  -   */
  -  public void debug(String messagePattern, Object arg1, Object arg2) {
  -    if (repository.isDisabled(Level.DEBUG_INT)) {
  -      return;
  -    }
  -    if (Level.DEBUG.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      messagePattern = MessageFormatter.format(messagePattern, arg1, arg2);
  -      forcedLog(FQCN, Level.DEBUG, messagePattern, null);
  -    }
  -  }
   
     /**
      Log a message object with the <code>DEBUG</code> level including
  @@ -348,62 +293,6 @@
         forcedLog(FQCN, Level.ERROR, message, null);
     }
   
  -
  -/**
  -   * Log a message with the <code>ERROR</code> level with message formatting
  -   * done according to the value of <code>messagePattern</code> and 
  -   * <code>arg</code> parameters.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   * 
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg The argument to replace the formatting element, i,e, 
  -   * the '{}' pair within <code>messagePattern</code>.
  -   * @since 1.2.10
  -   */
  -  public void error(Object messagePattern, Object arg) {
  -    if (repository.isDisabled(Level.ERROR_INT)) {
  -      return;
  -    }
  -
  -    if (Level.ERROR.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      if (messagePattern instanceof String){
  -        String msgStr = (String) messagePattern;
  -        msgStr = MessageFormatter.format(msgStr, arg);
  -        forcedLog(FQCN, Level.ERROR, msgStr, null);
  -      } else {
  -        // To be failsafe, we handle the case where 'messagePattern' is not
  -        // a String. Unless the user makes a mistake, this should never happen.
  -        forcedLog(FQCN, Level.ERROR, messagePattern, null);
  -      }
  -    }
  -  }
  -  
  -  /**
  -   * Log a message with the <code>ERROR</code> level with message formatting
  -   * done according to the messagePattern and the arguments arg1 and arg2.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   *
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg1 The first argument to replace the first formatting element
  -   * @param arg2 The second argument to replace the second formatting element
  -   * @since 1.2.10
  -   */
  -  public void error(String messagePattern, Object arg1, Object arg2) {
  -    if (repository.isDisabled(Level.ERROR_INT)) {
  -      return;
  -    }
  -    if (Level.ERROR.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      messagePattern = MessageFormatter.format(messagePattern, arg1, arg2);
  -      forcedLog(FQCN, Level.ERROR, messagePattern, null);
  -    }
  -  }
  -
     /**
      Log a message object with the <code>ERROR</code> level including
      the stack trace of the {@link Throwable} <code>t</code> passed as
  @@ -766,60 +655,6 @@
     }
   
     /**
  -   * Log a message with the <code>INFO</code> level with message formatting
  -   * done according to the value of <code>messagePattern</code> and 
  -   * <code>arg</code> parameters.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   * 
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg The argument to replace the formatting element, i,e, 
  -   * the '{}' pair within <code>messagePattern</code>.
  -   * @since 1.2.10
  -   */
  -  public void info(Object messagePattern, Object arg) {
  -    if (repository.isDisabled(Level.INFO_INT)) {
  -      return;
  -    }
  -
  -    if (Level.INFO.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      if (messagePattern instanceof String){
  -        String msgStr = (String) messagePattern;
  -        msgStr = MessageFormatter.format(msgStr, arg);
  -        forcedLog(FQCN, Level.INFO, msgStr, null);
  -      } else {
  -        // To be failsafe, we handle the case where 'messagePattern' is not
  -        // a String. Unless the user makes a mistake, this should never happen.
  -        forcedLog(FQCN, Level.INFO, messagePattern, null);
  -      }
  -    }
  -  }
  -  
  -  /**
  -   * Log a message with the <code>INFO</code> level with message formatting
  -   * done according to the messagePattern and the arguments arg1 and arg2.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   *
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg1 The first argument to replace the first formatting element
  -   * @param arg2 The second argument to replace the second formatting element
  -   * @since 1.2.10
  -   */
  -  public void info(String messagePattern, Object arg1, Object arg2) {
  -    if (repository.isDisabled(Level.INFO_INT)) {
  -      return;
  -    }
  -    if (Level.INFO.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      messagePattern = MessageFormatter.format(messagePattern, arg1, arg2);
  -      forcedLog(FQCN, Level.INFO, messagePattern, null);
  -    }
  -  }
  -  /**
      Log a message object with the <code>INFO</code> level including
      the stack trace of the {@link Throwable} <code>t</code> passed as
      parameter.
  @@ -918,33 +753,6 @@
       return Level.INFO.isGreaterOrEqual(this.getEffectiveLevel());
     }
   
  -  /**
  -    Check whether this category is enabled for the info Level.
  -    See also {@link #isDebugEnabled}.
  -
  -    @return boolean - <code>true</code> if this category is enabled
  -    for level WARN, <code>false</code> otherwise.
  -    @since 1.2.10
  -  */
  -  public boolean isWarnEnabled() {
  -    if(repository.isDisabled(Level.WARN_INT))
  -      return false;
  -    return Level.WARN.isGreaterOrEqual(this.getEffectiveLevel());
  -  }
  -
  -  /**
  -    Check whether this category is enabled for the info Level.
  -    See also {@link #isDebugEnabled}.
  -
  -    @return boolean - <code>true</code> if this category is enabled
  -    for level ERROR, <code>false</code> otherwise.
  -    @since 1.2.10
  -  */
  -  public boolean isErrorEnabled() {
  -    if(repository.isDisabled(Level.ERROR_INT))
  -      return false;
  -    return Level.ERROR.isGreaterOrEqual(this.getEffectiveLevel());
  -  }
   
     /**
        Log a localized message. The user supplied parameter
  @@ -1191,60 +999,6 @@
         forcedLog(FQCN, Level.WARN, message, null);
     }
   
  - /**
  -   * Log a message with the <code>WARN</code> level with message formatting
  -   * done according to the value of <code>messagePattern</code> and 
  -   * <code>arg</code> parameters.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   * 
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg The argument to replace the formatting element, i,e, 
  -   * the '{}' pair within <code>messagePattern</code>.
  -   * @since 1.2.10
  -   */
  -  public void warn(Object messagePattern, Object arg) {
  -    if (repository.isDisabled(Level.WARN_INT)) {
  -      return;
  -    }
  -
  -    if (Level.WARN.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      if (messagePattern instanceof String){
  -        String msgStr = (String) messagePattern;
  -        msgStr = MessageFormatter.format(msgStr, arg);
  -        forcedLog(FQCN, Level.WARN, msgStr, null);
  -      } else {
  -        // To be failsafe, we handle the case where 'messagePattern' is not
  -        // a String. Unless the user makes a mistake, this should never happen.
  -        forcedLog(FQCN, Level.WARN, messagePattern, null);
  -      }
  -    }
  -  }
  -  /**
  -   * Log a message with the <code>WARN</code> level with message formatting
  -   * done according to the messagePattern and the arguments arg1 and arg2.
  -   * <p>
  -   * This form avoids superflous parameter construction. Whenever possible,
  -   * you should use this form instead of constructing the message parameter 
  -   * using string concatenation.
  -   *
  -   * @param messagePattern The message pattern which will be parsed and formatted
  -   * @param arg1 The first argument to replace the first formatting element
  -   * @param arg2 The second argument to replace the second formatting element
  -   * @since 1.2.10
  -   */
  -  public void warn(String messagePattern, Object arg1, Object arg2) {
  -    if (repository.isDisabled(Level.WARN_INT)) {
  -      return;
  -    }
  -    if (Level.WARN.isGreaterOrEqual(this.getEffectiveLevel())) {
  -      messagePattern = MessageFormatter.format(messagePattern, arg1, arg2);
  -      forcedLog(FQCN, Level.WARN, messagePattern, null);
  -    }
  -  }
  -
     /**
      Log a message with the <code>WARN</code> level including the
      stack trace of the {@link Throwable} <code>t</code> passed as
  
  
  
  1.16.2.3  +1 -2      logging-log4j/src/java/org/apache/log4j/Logger.java
  
  Index: Logger.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/Logger.java,v
  retrieving revision 1.16.2.2
  retrieving revision 1.16.2.3
  diff -u -r1.16.2.2 -r1.16.2.3
  --- Logger.java	28 Apr 2005 20:34:04 -0000	1.16.2.2
  +++ Logger.java	6 May 2005 05:32:36 -0000	1.16.2.3
  @@ -8,7 +8,6 @@
   package org.apache.log4j;
   
   import org.apache.log4j.spi.LoggerFactory;
  -import org.slf4j.ULogger;
   
   
   /**
  @@ -18,7 +17,7 @@
     @since log4j 1.2
   
     @author Ceki G&uuml;lc&uuml; */
  -public class Logger extends Category implements ULogger {
  +public class Logger extends Category {
   
     /**
        The fully qualified name of the Level class. See also the
  
  
  
  No                   revision
  No                   revision
  1.14.2.1  +9 -14     logging-log4j/src/xdocs/Attic/contactUs.xml
  
  Index: contactUs.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/Attic/contactUs.xml,v
  retrieving revision 1.14
  retrieving revision 1.14.2.1
  diff -u -r1.14 -r1.14.2.1
  --- contactUs.xml	9 May 2002 15:43:44 -0000	1.14
  +++ contactUs.xml	6 May 2005 05:32:36 -0000	1.14.2.1
  @@ -2,7 +2,7 @@
   <document>
   
     <properties>
  -    <author email="cgu@apache.org">Ceki Gulcu</author>
  +    <author email="ceki at apache.org">Ceki Gulcu</author>
       <title>Contact us</title>
     </properties>
   
  @@ -14,21 +14,16 @@
         <p>Discussion on log4j and logging in general are held on the
   	<em>log4j-user</em> mailing list.  To subscribe to this list
   	send an e-mail to <a
  -	HREF="mailto:log4j-user-subscribe@jakarta.apache.org">log4j-user-subscribe@jakarta.apache.org</a>.
  +	HREF="mailto:log4j-user-subscribe@logging.apache.org">log4j-user-subscribe@logging.apache.org</a>.
         </p>
   
         <p>Development related discussions are held on the
   	<em>log4j-dev</em> mailing list. To subscribe to this list
   	send an e-mail to <A
  -	HREF="mailto:log4j-dev-subscribe@jakarta.apache.org">log4j-dev-subscribe@jakarta.apache.org</A>.</p>
  -
  -      <p>All developers are encouraged to subscribe to the
  -	<em>log4j-cvs</em> list which will notify the subscribers of
  -	CVS any commits to the repository.  To subscribe to this list
  -	send an e-mail to <A
  -	HREF="mailto:log4j-cvs-subscribe@jakarta.apache.org">log4j-cvs-subscribe@jakarta.apache.org</A>.
  -	Committers <em>should</em> subscribe to this list with their
  -	Apache e-mail address.
  +	HREF="mailto:log4j-dev-subscribe@logging.apache.org">log4j-dev-subscribe@logging.apache.org</A>. All
  +	developers are encouraged to subscribe to the
  +	<em>log4j-dev</em> list which will notify the subscribers of
  +	any commits to our CVS repository.
         </p>
   
         <p><b>To prevent spam, we expect you to be subscribed to a list
  @@ -37,7 +32,7 @@
   	  creates needless work for us.</b>
         </p>
   
  -      <p>Most Jakarta mailing lists, in particular the log4j mailing
  +      <p>Most Logging Services mailing lists, in particular the log4j mailing
   	lists, are archived. Some of the known archives are listed
   	below:
         </p>
  @@ -48,9 +43,9 @@
   	  <a href="http://www.mail-archive.com/">http://www.mail-archive.com</a>
   	</li>
   
  -	<li>Full mbox archives of all Jakarta lists are available at
  +	<li>Full mbox archives of all Logging Services lists are available at
   	    <a
  -	    href="http://jakarta.apache.org/mail/">http://jakarta.apache.org/mail/</a>
  +	    href="http://logging.apache.org/mail/">http://logging.apache.org/mail/</a>
   	</li>
   
   	<li>
  
  
  
  1.7.2.3   +82 -10    logging-log4j/src/xdocs/contributors.xml
  
  Index: contributors.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/contributors.xml,v
  retrieving revision 1.7.2.2
  retrieving revision 1.7.2.3
  diff -u -r1.7.2.2 -r1.7.2.3
  --- contributors.xml	18 Jun 2002 14:11:38 -0000	1.7.2.2
  +++ contributors.xml	6 May 2005 05:32:36 -0000	1.7.2.3
  @@ -14,9 +14,12 @@
   	more prominent contributors are listed below in alphabetical
   	order.
         </p>
  +    <ul>
   
  -      <ul>
  -
  +    <!-- ======================================== -->
  +    <!-- LISTED IN ALPHABETICAL ORDER (last name) -->
  +    <!-- ======================================== -->
  +    
   	<li><b>Mathias Bogaert</b> 
   
   	  <p>While not lurking on <a
  @@ -39,13 +42,31 @@
   
   	<li><b>Ceki G&#252;lc&#252;</b> 
   
  -	  <p>Ceki is the founder the log4j project which still takes
  -	  much of his time. He enjoys writing software altough he is
  -	  discovering that it is far more difficult than it looks. He
  -	  is also slowly building an IT services company called <a
  -	  href="http://qos.ch">qos.ch</a>.
  -	  </p>
  -	</li>
  +          <table>
  +          <tr><td> <p>Ceki is the founder the log4j project which
  +          continues to occupy much of his time. He enjoys writing
  +          software altough he is discovering that it is far more
  +          difficult than what it may seem initially. He is also
  +          managing his <a href="http://www.qos.ch">IT services
  +          company</a>.</p></td> 
  +          <td><img src="images/ceki-72x101.gif"></img></td>
  +         </tr>
  +         </table>
  +	</li>
  +
  +    <li><b>Jacob Kjome</b> 
  +
  +        <p>Jacob Kjome has been developing software
  +	  since 1997 and has been playing with Java for about 4 years.
  +	  Jake joined the log4j team after being very active on the
  +	  user list and contributing servlet and repository selector
  +	  related code to the logj-sandbox.  He is also a committer on
  +	  the (non-Apache related) XMLC, BarracudaMVC, and Prevayler
  +	  projects.  Of late his free time has been squeezed with a
  +	  new job and his vigorous 2 year old son, Nicholas, but he
  +	  still tries to pitch in when he can. :-)
  +        </p>
  +    </li>
   
   
   	<li><b>Anders Kristensen</b> 
  @@ -63,6 +84,21 @@
   	  </p>
   	</li>
   
  +    <li><b>Yoav Shapira</b> 
  +      <table>
  +        <tr><td>
  +          <p>Yoav Shapira works for Millennium Pharmaceuticals and
  +          is as interested in the business aspects of Open-Source
  +          Software as he is in the technical aspects. Yoav contributes
  +          to the Tomcat container, the Log4j logging system, and a
  +          number of jakarta-commons and other open-source projects.
  +              </p>
  +        </td>
  +        <td><img align="right" src="images/yshapira.bmp"></img></td>
  +       </tr>
  +     </table>
  +   </li>
  +
   	<li><b>Jon Skeet</b> 
   
   	  <p>Jon is a software developer in his mid-twenties living in
  @@ -74,6 +110,24 @@
   	  </p>
   	</li>
   
  +	<li><b>Paul Smith</b> 
  +      <table>
  +        <tr><td>
  +        <p>Paul Smith has been developing software since 1990, and playing 
  +	    computer games a few years longer than that.  He has been thoroughly
  +	    enjoying Java since 1998 after he gave up on Visual Basic in disgust.
  +	    Paul joined the log4j team after finding how darn useful it and the 
  +	    companion Chainsaw application was in '03, and has been helping out 
  +	    where he can, working on Chainsaw v2, and generally making a good 
  +	    nuisance of himself.
  +	    </p></td>
  +        <td><img align="right" src="images/psmith.jpg"></img></td>
  +       </tr>
  +     </table>
  +	
  +
  +    </li>
  +
   	
   	<li><b>Chris Taylor</b> 
   	  
  @@ -83,9 +137,27 @@
   	  href="jakarta.apache.org/ant/">jakarta-ant</a>.
   	  </p>
   	</li>
  +
  +	<li><b>Mark Womack</b> 
  +
  +         <table>
  +          <tr><td>  <p>Mark Womack has been developing software for over 12
  +	  years. He has been developing in Java for the past 4 years,
  +	  focusing on web application development. He has been an
  +	  active committer for the Apache Jakarta log4j project since
  +	  April 2002, contributing features for the upcoming v1.3
  +	  release. </p></td> 
  +          <td><img src="images/mark-72x99.gif"></img></td>
  +         </tr>
  +         </table>
   	
  -      </ul>
  +       
  +                                      
  +	 
  +    </li>
   
  +         
  +      </ul>
       </section>
       
     </body>
  
  
  
  1.15.2.7  +162 -76   logging-log4j/src/xdocs/documentation.xml
  
  Index: documentation.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/documentation.xml,v
  retrieving revision 1.15.2.6
  retrieving revision 1.15.2.7
  diff -u -r1.15.2.6 -r1.15.2.7
  --- documentation.xml	18 Feb 2003 16:50:13 -0000	1.15.2.6
  +++ documentation.xml	6 May 2005 05:32:36 -0000	1.15.2.7
  @@ -2,55 +2,56 @@
   <document>
   
     <properties>
  -    <author email="ceki@apache.org">Ceki Gulcu</author>
  +    <author email="">Ceki Gulcu</author>
  +    <author email="yoavs@apache.org">Yoav Shapira</author>
       <title>Documentation</title>
     </properties>
   
  -<body>
  +  <body>
   
       <section name="Official log4j documentation">
  -
  +      
         <p>With the exception of the complete manual, the following
  -	documentation is included with the standard log4j distribution
  -	and also browsable online:
  +      documentation is included with the standard log4j distribution
  +      and also browsable online:
         </p>
         
         <ul>
  -	<p>
  -	  <a
  -	  href="https://www.qos.ch/shop/products/clm_t.jsp"><img
  -	  align="right" src="images/coverSmall.png"></img></a> <li><a
  -	  href="manual.html"><b>short manual</b></a>,
  -	  </li>
  -	</p>
  -
  -	<p>
  -	  <li><a href="https://www.qos.ch/shop/products/clm_t.jsp"><b>complete manual</b></a> (commercial), 
  -	  </li>
  -	</p>
  +        <p>
  +          <a
  +           href="http://www.qos.ch/shop/products/eclm/"><img
  +           align="right" src="images/coverSmall.png"></img></a> <li><a
  +           href="manual.html"><b>short manual</b></a>, 
  +           </li>
  +        </p>
  +        
  +        <p>
  +          <li><a href="http://www.qos.ch/shop/products/eclm/"><b>complete manual</b></a> (commercial), 
  +          </li>
  +        </p>
  +        
  +        <p>
  +          <li>
  +            <a href="api/index.html"><b>javadoc documentation</b></a>,
  +          </li>
  +        </p>
  +        
  +        <p>
  +          <li> 
  +            <a href="chainsaw.html"><b>Chainsaw documentation</b></a>,
  +          </li>
  +        </p>
  +        
  +        <p>
  +          <li>
  +            <a href="HISTORY"><b>project history</b></a>,
  +          </li>
  +        </p>
   	
  -	<p>
  -	  <li>
  -	    <a href="api/index.html"><b>javadoc documentation</b></a>,
  -	  </li>
  -	</p>
  -
  -	<p>
  -	  <li>
  -	    <a href="lf5/overview.html"><b>LogFactor5 documentation</b></a>,
  -	  </li>
  -	</p>
   	
   	<p>
   	  <li>
  -	    <a href="HISTORY"><b>project history</b></a>,
  -	  </li>
  -	</p>
  -	
  -	
  -	<p>
  -	  <li>
  -	    <a href="FAQ.html"><b>FAQ</b></a>,
  +	    <a href="faq.html"><b>FAQ</b></a>,
   	  </li>
   	</p>
   	
  @@ -62,67 +63,152 @@
   	
         </ul>
       </section>
  +
  +    <section name="Translations to other languages">
  +       <ul>
  +         <li><a
  +         href="http://www.vimeworks.com/~mauricio/manualLog4J.html">Spanish
  +         translation</a> of the short manual Mauricio Santacruz (<a href="http://www.vimeworks.com/~mauricio/manualLog4J.pdf">PDF</a>, <a href="http://www.vimeworks.com/~mauricio/manualLog4J.html">HTML</a>)</li>
  +         <li><a href="http://www.javacore.de/jumpToDownload.php?id=8&amp;url=tutorials/schnelle/log4jmanual.pdf">German translation</a> of the short manual, courtesy of Dirk Schnelle. (PDF only at this time)</li>
  +      </ul>
  +    </section>
  +    
       
       <section name="Articles on log4j">
         <ul>
  -
  -	<p>
  -	  <li><a href="http://www.vipan.com/htdocs/log4jhelp.html">Don't Use System.out.println!
  -	    Use Log4j</a> by Vipan Singla
  -	  </li>
  -	</p>
  -
  -	<p><li><a href="http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html?page=1">
  -	    Build Flexible Logs With log4j</a> by Vikram Goyal
  -	</li></p>
  -
  -	<p><li><a
  -	href="http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/log4j/log4j.html">log4j</a>
  -	by Ashley J.S Mills, University Of Birmingham</li></p>
  -
  -	<p><li><a href="http://www.builder.com.com/article.jhtml?id=u00820020124kev01.htm">
  -	    Add logging to your Java Applications</a> by Kevin Brown
  -	</li></p>
  -	
  -	<p><li><a href="http://www.builder.com.com/article.jhtml?id=u00220020724kev01.htm">
  -	    How does the Java logging API stack up against log4j?</a> by Kevin Brown
  -	</li></p>
  -
  -	<p><li>
  -	  <a href="http://www.opensymphony.com/guidelines/logging.jsp">OpenSymphony Logging Primer</a>
  -	</li></p>
  -
  -	<p><li>
  +        
  +        <p>
  +          <li><a href="http://www.vipan.com/htdocs/log4jhelp.html">Don't Use System.out.println!
  +          Use Log4j</a> by Vipan Singla
  +          </li>
  +        </p>
  +        
  +        <p><li><a href="http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html?page=1">
  +        Build Flexible Logs With log4j</a> by Vikram Goyal
  +        </li></p>
  +        
  +        <p><li><a
  +        href="http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/log4j/log4j.html">log4j</a>
  +        by Ashley J.S Mills, University Of Birmingham</li></p>
  +        
  +        <p><li><a href="http://www.builder.com.com/article.jhtml?id=u00820020124kev01.htm">
  +        Add logging to your Java Applications</a> by Kevin Brown
  +        </li></p>
  +        
  +        <p><li><a href="http://www.builder.com.com/article.jhtml?id=u00220020724kev01.htm">
  +        How does the Java logging API stack up against log4j?</a> by Kevin Brown
  +        </li></p>
  +        
  +        <p>
  +          <li>
  +            <a href="http://www.opensymphony.com/guidelines/logging.jsp">OpenSymphony Logging Primer</a>
  +          </li>
  +        </p>
  +        
  +        <p><li>
   	  <a href="http://www.jguru.com/faq/Log4j">log4j FAQ</a> at jGuru
   	</li></p>
   
   	<p><li>
  -	  <a href="http://qos.ch/logging/thinkAgain.html">Think Again</a> by Ceki G&#252;lc&#252;
  +	  <a href="http://www.qos.ch/logging/thinkAgain.html">Think Again</a> by Ceki G&#252;lc&#252;
   
   	</li></p>
   
  -	<p><li> <a href="http://qos.ch/logging/sc.html">Supporting the
  +	<p><li> <a href="http://www.qos.ch/logging/sc.html">Supporting the
   	  log4j <code>RepositorySelector</code></a> by Ceki
   	  G&#252;lc&#252;
   	</li></p>
   
  -         <p><li> <a href="http://rei1.m-plify.com/log4j/">Log4j class
  +         <p><li> <a href="http://rei1.m-plify.net/log4j/">Log4j class
            diagrams</a>, courtesy of David Tonhofer
               </li>
            </p>
   
  -	<p><li> <a href="http://www.jug-l.org/log4j.html">Advanced
  -	  Log4j</a> Louisville JUG presentation by Jonathan Cowherd </li></p>
  -      </ul> 
  +         <p><li> <a
  +         href="http://www.onjava.com/pub/a/onjava/2003/04/02/log4j_ejb.html">Understanding
  +         Classloaders: log4j in a J2EE Environment</a> by Vikram Goyal
  +            </li>
  +         </p>
   
  -      <p>If you would like your log4j-relateed article to be listed
  -	  here, then please send a note to the <a
  -	  href="mailto:log4j-user@jakarta.apache.org">log4j-user@jakarta.apache.org</a>
  -	  list.
  -      </p>
   
  +         <p><li> <a
  +         href="http://www.linux-magazin.de/Artikel/ausgabe/2002/04/coffee/coffee.html">Logging
  +         f&#252;r Java-Programme, Zu den Akten</a> by Bernhard Bablok
  +         in Linux Magazine, 04/2002.
  +            </li>
  +         </p>
  +
  +         <p><li> <a
  +         href="http://www-106.ibm.com/developerworks/java/library/j-instlog/">Instant logging: Harness the power of log4j with Jabber</a> by Ruth Zamorano and Rafael Luque, in developerWorks 2003
  +         </li>
  +         </p>
   
  +         <p>
  +           <li> <a
  +           href="http://developers.sun.com/prodtech/appserver/reference/techart/log4j.html">Using Log4j in the Sun Java System Application Server</a> by Matthew Litkey, Jay Galvin, and Marina Sum, from Sun.
  +           </li>
  +         </p>
  +         
  +         <p>
  +           <li> <a
  +           href="http://www.onjava.com/pub/a/onjava/2004/09/29/smtp-logging.html">Reporting
  +           Application Errors by Email</a> by Sean C. Sullivan,
  +           2004-09-24, published by O'Reilly.
  +           </li>
  +         </p>
  +         
  +      </ul> 
       </section>
  -</body>
  +   
  +    <section name="Log4j presentations">
  +       <ul>
  +
  +
  +         <p><li> <a href="http://www.jug-l.org/log4j.html">Advanced
  +         Log4j</a> Louisville JUG presentation by Jonathan Cowherd </li></p>
  +         
  +         <p><li><a href="http://www.johnmunsch.com/projects/Presentations/">Log4J
  +         In 30 Minutes Or Less</a> by John Munsch</li></p>
  +         
  +         <p><li><a href="https://www.qos.ch/ac2001/F11-10.html">Log4j, a logging package for the Java language</a> by Ceki G&#252;lc&#252;</li></p>
  +         
  +         <p><li><a
  +         href="http://www.ejug.org/OpenSource%20Log4j2_files/frame.htm">Log4j presentation by the</a>
  +         Edmonton Java Users Group</li></p>
  +         
  +         <p><li><a href="http://www.ociweb.com/javasig/knowledgebase/January2001/Log4J.ppt">Log4j</a> by Brent Twenter
  +         </li></p>
  +      </ul>
  +    </section>
  +    
  +    
  +    <section name="Training &amp; Professional support">
  +      <p>The following organisations offer log4j-related consultancy
  +      and training services. Their inclusion on this page does
  +      not imply endorsement by the Apache Software Foundation.	  
  +      </p>
  +      
  +      <ul>
  +        <li><a
  +        href="https://www.qos.ch/shop/products/profSupport/">QOS.ch,
  +        Switzerland</a> proposes professional support contracts.
  +        </li>
  +      </ul>
  +      
  +      <ul>
  +        <li><a
  +        href="http://www.thegoodsoftwarecompany.com/log4jTraining.do">The
  +        Good Software Company</a> proposes log4j training courses.
  +        </li>
  +      </ul>
  +      
  +      <p><b>If you would like your log4j-related article or service
  +      to be listed here, then please send a note to the <a
  +      href="mailto:log4j-user@logging.apache.org">log4j-user@logging.apache.org</a>
  +      list.</b>
  +      </p>
  +    </section>
  +
  +  </body>
   </document>
   
  
  
  
  1.53.2.14 +184 -93   logging-log4j/src/xdocs/download.xml
  
  Index: download.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/download.xml,v
  retrieving revision 1.53.2.13
  retrieving revision 1.53.2.14
  diff -u -r1.53.2.13 -r1.53.2.14
  --- download.xml	18 Feb 2003 16:50:13 -0000	1.53.2.13
  +++ download.xml	6 May 2005 05:32:36 -0000	1.53.2.14
  @@ -6,55 +6,45 @@
       <title>Download</title>
     </properties>
   
  -  <meta name="keywords" content="java, logging, tracing, component, framework, API, log4j"/>
  -<body>
  -
  -    <section name="log4j version 1.2.8">
  -      <p>log4j 1.2.8 is available in <a
  -	href="../jakarta-log4j-1.2.8.tar.gz"><b>TAR.GZ</b></a> format
  -	or in <a href="../jakarta-log4j-1.2.8.zip"><b>ZIP</b></a>
  -	format.
  -      </p>
  -
  -      <p>As of release 1.2.8 log4j now searches for the file log4j.xml
  -        as well as the file log4j.properties during
  -        initialization. See the <a href="HISTORY">HISTORY</a> file for
  -        the firther details.
  -      </p>
  -      
  -      <p>In addition to many performance improvements, bug fixes, and
  -	other small enhancements, log4j 1.2 adds JMX support, Mapped
  -	Diagnostic Contexts, JDBC logging, graphical log viewer
  -	(chainsaw), and buffered IO capability. One important change
  -	is the replacement of the <code>Category</code> class with
  -	<code>Logger</code> class and the <code>Priority</code> class
  -	with the <code>Level</code> class in order to facilitate
  -	migrating from the JDK 1.4 logging API to log4j. <a
  -	href="http://www.javaworld.com/javaworld/jw-05-2001/jw-0504-finalists.html"><img
  -	src="images/ecaward_finalist_logo.gif" align="right"
  -	border="0"/></a>
  -      </p>
  -
  -	<p>Version 1.2 is the 22nd major public release of log4j.  All
  -	changes except the removal of deprecated methods are backward
  -	compatible such that log4j 1.2 can be considered a drop in
  -	replacement for log4j 1.1.3. The only exception is the
  -	renaming of the <code>CategoryFactory</code> class to
  -	<code>LoggerFactory</code> class such that subclasses of
  -	<code>Category</code> class must be modified and
  -	recompiled. <em>The recommended pattern for extending the
  -	<code>Logger</code> class is wrapping. Moreover, we strongly
  -	discourage casual users from subclassing the
  -	<code>Category</code> or <code>Logger</code> classes. </em>
  -      </p>
  -
  -      <p>We also maintain a list of <a href="earlier.html">earlier
  -	  versions</a> of log4j for download, intended for the curious
  -	  paleontologist -- there seems to be quite a few of them!
  -      </p>
  -
  +    <meta name="keywords" content="java, log4j download, logging, tracing, component, framework, API, log4j"/>
  +      <body>
  +	
  +      <section name="log4j version 1.2.9">
  +	<p>Log4j is <a
  +	      href="http://logging.apache.org/site/binindex.cgi"><b>available
  +	      for download</b></a> from a number of mirrors. Please
  +	      use these mirrors as they improve download time and save
  +	      bandwidth.
  +	  </p>
  +	  
  +	  <p>Log4j version 1.2.9, is identical to version 1.2.8,
  +	  except that several key methods have been deprecated in
  +	  preparation for version 1.3.0, the next major release of
  +	  log4j. These changes are intended to enforce the rule that
  +	  client code should never refer to the <code>Category</code>
  +	  class directly, but use the <code>Logger</code> class
  +	  instead. Similarly, client code should not refer to the
  +	  <code>Priority</code> class but to the <code>Level</code>
  +	  class instead.
  +          </p>
  +
  +          <p>See the document entitled <a
  +          href="http://www.qos.ch/logging/preparingFor13.jsp">preparing
  +          for log4j 1.3</a> for a more detailed discussion.
  +          </p>
  +          
  +          
  +
  +	  <subsection name='Earlier Releases'>
  +	    <p>We also maintain <a
  +	      href="earlier.html">earlier
  +	      versions of log4j</a> for download, intended for the
  +	      curious paleontologist -- there seems to be quite a few
  +	      of them!
  +	    </p>
  +	  </subsection>
   
  -    </section>
  +	</section>
   
   
       <section name="Third-party extensions (listed in alphabetical order)">
  @@ -64,15 +54,27 @@
   	<!-- ============================================================================== -->
   	
   	<dt><a
  -	href="http://logui.sourceforge.net/"><b>Chainsaw</b></a></dt>
  -	<dd><b>Chainsaw is now integrated with log4j and ships with
  -	the official distribution.</b> Chainsaw is a graphical log
  -	viewer and filter for the log4j package. It listens for <a
  -	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/spi/LoggingEvent.html">LoggingEvent</a>
  -	objects sent using the <a
  -	href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SocketAppender.html">SocketAppender</a>
  -	and displays them in a table. Chainsaw also supports loading
  -	events from files in <code>XMLLayout</code> format.
  +	href="chainsaw.html"><b>Chainsaw v2 (NEW!)</b></a></dt>
  +
  +	<dd>A new and improved version of the venerable Chainsaw
  +	utility, now being written by the log4j development team is
  +	getting closer to release.  You can see screen shots of it and
  +	install it and run over <A href="chainsaw.html">here</A>
  +	</dd>
  +
  +	<!-- ============================================================================== -->
  +	<dt><a href="http://minaret.biz/tips/datedFileAppender.html"><b>DatedFileAppender</b></a></dt>
  +
  +	<dd><code>DatedFileAppender</code> works in the same manner as
  +	the Tomcat FileLogger. Contrary to
  +	<code>DailyRollingFileAppender</code> shipping with log4j, log
  +	file names generated by <code>DatedFileAppender</code> always
  +	contain today's date. While this distinction seems minor, it
  +	means you can reliably copy, compress, remove or manipulate a
  +	day's log file shortly after midnight. With the
  +	<ocde>DailyRollingFileAppender</ocde>, a day's log file is not
  +	renamed until the first message is logged some time after
  +	midnight.
   	</dd>
   
   	<!-- ============================================================================== -->
  @@ -86,7 +88,7 @@
   
   	<dt>
   	  <a
  -	href="http://www.mannhaupt.com/danko/projects/"><b>JDBCAppender</b></a>
  +	href="http://www.dankomannhaupt.de/projects/index.html"><b>JDBCAppender</b></a>
   	</dt> 
   
           <dd>A powerful <code>JDBCAppender</code> by Danko Mannhaupt
  @@ -95,9 +97,47 @@
   	  log4j 1.2. 
   	</dd>
   
  +       <!-- ============================================================================== -->
  +
  +	<dt>
  +	  <a
  +	href="http://just4log.sf.net/"><b>Just4log</b></a>
  +	</dt> 
  +
  +        <dd>Just4Log is a library to enhance dynamically the
  +        performance of various logging systems inside a java
  +        application. Dynamically because the sourcecode in java is not
  +        modified but rather the optimization occurs on the compiled
  +        ByteCode files.
  +	</dd>
  +
  +     <!-- ============================================================================== -->	
  +	<dt><a href="http://purl.net/jware/antx/"><b>log4Ant</b></a></dt>
  +
  +	<dd>log4Ant includes a complete bridge to the Log4J logging systemfor a robust build monitoring system. 
  +	These Ant components let you capture, map, and send Ant log messages and stdio output through your Log4J installation.  Contact <a href="maito:contact@jware.info">contact@jware.info</a>
  +        </dd>
  +     <!-- ============================================================================== -->	
  +
  +	<dt><a href="http://log4j400.sourceforge.net/"><b>log4j400</b></a></dt>
  +
  +	<dd>Log4J400 includes MessageQueue and DataQueue Appenders for
  +	the AS/400 (aka IBM iSeries).
  +        </dd>
  +
  +    <!-- ============================================================================== -->	
  +	
  +	<dt><a href="http://sourceforge.net/projects/log4j2db"><b>log4j2db</b></a></dt>
  +
  +	<dd>This Project provides a set of EJBs to store Log4J events
  +	(received via JMS appender) in a database. The main aim is to
  +	provide a toolset for a centralized, data-center suitable
  +	logging.
  +        </dd>
  +
   	<!-- ============================================================================== -->	
   	
  -	<dt><a href="http://qos.ch/"><b>log4j<em>ME</em></b></a></dt>
  +	<dt><a href="http://cvs.apache.org/viewcvs/jakarta-log4j/log4jMini/"><b>log4j<em>ME</em></b></a></dt>
   
   	<dd>Log4j<em>ME</em>, or log4j MiniEdition, is based on the
   	same code as log4j. However, as the name indicates the
  @@ -106,40 +146,39 @@
   	compatible with log4j standard edition. You can choose to
   	upgrade to log4j standard edition at any time by replacing
   	<em>log4jME.jar</em> with <em>log4j.jar</em> in your
  -	classpath.
  +	classpath. At this time, log4jME is only available through
  +	CVS.
   	</dd>
  +	
  +       <!-- ============================================================================== -->	
  +	
  +	<dt><a href="http://www.openfuture.de/Log4Unit/"><b>log4<em>Unit</em></b></a></dt>
   
  -	<!-- ============================================================================== -->
  -
  -	<dt><a href="http://www.launchsoftware.com"><b>LogWeb</b></a> (commercial) </dt>
  -
  -	<dd>Log4Web is a J2EE web application, designed to web-enable
  -	  system log files that have been generated by log4j.
  +	<dd>Log4Unit is a <a
  +	href="http://www.junit.org/index.htm">JUnit</a> extension
  +	combining JUnit with Log4J. The intention is to create test
  +	protocols for JUnit.
  +
  +        <p>JUnit is asymmetrical in the sense that it focusses on the
  +        documentation of test failures and errors. Successful
  +        execution of a test case is not further documented. In order
  +        to obtain a test protocol that documents the initial settings,
  +        the test case execution and its results, a logging component
  +        is required. Log4J as the current de facto standard is
  +        selected for this extension.
  +        </p>
   	</dd>
   
   	<!-- ============================================================================== -->
   
  -	<dt><a
  -	    href="http://traxel.com/lumbermill/"><b>Lumbermill</b></a></dt>
  -	<dd>Lumbermill is a Swing(tm) log processing and distribution
  -	  system for Log4j. </dd>
  -	
  -	<!-- ============================================================================== -->
  -	
  -	<dt>
  -	  <a
  -	href="http://www.servidium.com/site/logfactor5/index.html"><b>LogFactor5</b>
  -	</a>(commercial)
  -	</dt> 
  +	<dt><a href="http://www.launchsoftware.com"><b>Log4Web</b></a> (commercial) </dt>
   
  -	<dd>Another full-featured graphical log viewer. After a merger
  -	  and the subsequent change in business-orientation, the
  -	  owners of LogFactor5 have decided to donate their product to
  -	  the log4j project.
  +	<dd>Log4Web is a J2EE web application, designed to web-enable
  +	  system log files that have been generated by log4j.
   	</dd>
   
   	<!-- ============================================================================== -->
  -	
  +		
   	<dt><a href="http://jakarta.apache.org/taglibs/doc/log-doc/intro.html">
   	    <b>Log Tag</b></a>
   	</dt>
  @@ -149,6 +188,16 @@
   
   	<!-- =========================================================================== -->
   
  +	<dt><a href="http://www.codeczar.com/products/logweb/index.html"><b>LogWeb</b></a> </dt>
  +
  +	<dd>LogWeb is a web interface for configuring log4j at runtime
  +	within a servlet container.  Every log4j feature of is
  +	configurable through this interface.
  +	</dd>
  +
  +	<!-- ============================================================================== -->
  +
  +
   	<dt><a href="http://www.m2technologies.net/asp/snmpTrapAppender.asp">
   	    <b>SNMPTrapAppender</b></a>
   	</dt>
  @@ -161,13 +210,50 @@
   
   	<!-- =========================================================================== -->
   
  +         <dt><a href="http://xpolog.com"><b>XpoLog</b></a>
  +	</dt>
  +
  +	<dd>Log view and analysis application which enables web
  +	browsing and analysis over logs.
  +	</dd>
  +
  +	<!-- =========================================================================== -->
  +
         </dl>
       </section>
       
  -    <section name="Ports to other languages">
  +    <section name="Ports to other languages (listed in alphabetical order within each section)">
  +
  +     <subsection name="Fellow Apache Logging Services Projects">
   
         <dl>	
   	<!-- =========================================================================== -->
  +
  +	<dt><a
  +	href="http://logging.apache.org/log4cxx/"><b>log4cxx</b></a></dt>
  +	<dd>Log4cxx is a port to C++ of the log4j project.</dd>
  +
  +	<!-- =========================================================================== -->	
  +	<dt><a
  +	href="http://logging.apache.org/log4net/"><b>log4net</b></a></dt>
  +
  +	<dd>The .NET implementation of the popular log4j Java API
  +	providing flexible and arbitrarily granular control over log
  +	management and configuration.</dd>
  +
  +	<!-- =========================================================================== --> 
  +        <dt><a href="http://logging.apache.org/log4php/"><b>log4php</b></a></dt> 
  +
  +        <dd>Log4Php is a PHP port of log4j framework. It supports xml configuration,
  +        logging to files, stdout/err, syslog, socket, configurable
  +        output layouts and logging levels. </dd>
  +
  +     </dl>
  +    </subsection>
  +
  +    <subsection name="Other Ports">
  +     <dl>
  +	<!-- =========================================================================== -->
   	<dt><a
   	href="http://log4c.sourceforge.net"><b>log4c</b></a></dt>
   
  @@ -187,7 +273,10 @@
   
   	<dt><a
   	href="http://log4cplus.sourceforge.net/"><b>log4cplus</b></a></dt>
  -	<dd>A competing port to C++.</dd> 
  +	<dd>Log4cplus is a simple to use C++ logging API providing
  +	thread-safe, flexible, and arbitrarily granular control over
  +	log management and configuration. It is modeled after the Java
  +	log4j API.</dd>
   
   	<!-- =========================================================================== -->
   	
  @@ -209,13 +298,14 @@
   	enhanced, however the current release is stable and has been
   	released to CPAN.
   	</dd>
  -	<!-- =========================================================================== -->	
  -	<dt><a
  -	href="http://www.neoworks.com/products/log4net/"><b>log4net</b></a></dt>
   
  -	<dd>The .NET implementation of the popular log4j Java API
  -	providing flexible and arbitrarily granular control over log
  -	management and configuration.</dd>
  +        <!-- ============================================================================== -->	
  +        <dt><a href="http://log4ls.sourceforge.net/"><b>log4LS</b></a></dt>
  +
  +        <dd>Log4LS is a LotusScript library package and is used to get
  +         logging statements to a Domino database, sent by mail or
  +         written to a file. It is modeled after Jakarta log4j.
  +         </dd>
   
   	<!-- =========================================================================== -->
   	<dt><a
  @@ -265,10 +355,11 @@
   	
   	<!-- =========================================================================== -->
         </dl>
  -      
  +
  +     </subsection>
         
         <p>If you would like your software to be listed here, then send a note to the <a
  -	  href="mailto:log4j-user@jakarta.apache.org">log4j-user@jakarta.apache.org</a>
  +	  href="mailto:log4j-user@logging.apache.org">log4j-user@logging.apache.org</a>
   	list.</p>
         
       </section>
  
  
  
  1.7.2.1   +4 -16     logging-log4j/src/xdocs/earlier.xml
  
  Index: earlier.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/earlier.xml,v
  retrieving revision 1.7
  retrieving revision 1.7.2.1
  diff -u -r1.7 -r1.7.2.1
  --- earlier.xml	4 Apr 2002 14:46:02 -0000	1.7
  +++ earlier.xml	6 May 2005 05:32:36 -0000	1.7.2.1
  @@ -12,27 +12,15 @@
   
         <hr/> 
         
  -      <p><b>BEWARE:</b> For some reason Internet Explorer decides to
  -	rename ".tar.gz" files as ".tar". You should rename the files back to
  +      <p><b>BEWARE:</b>Certain Internet Explorer versions rename .tar.gz downloads
  +        as .tar.  You should rename the files back to
   	<code>tar.gz</code> after the download completes.
         </p> 
         <hr/>
   
  -      <dl>
  -	<dt><b>jakarta-log4j-1.0.4</b></dt>
  -	<dd>
  -	  Download full package in <a href="../jakarta-log4j-1.0.4.tar.gz">TAR.GZ</a> 
  -	  format. 
  -	</dd>
  +      <a href="http://archive.apache.org/dist/logging/log4j/">Log4j Archives</a>
   
  -	<dt><b>jakarta-log4j-1.1.3</b></dt>
  -	<dd>
  -	  Download full package in <a href="../jakarta-log4j-1.1.3.tar.gz">TAR.GZ</a> 
  -	  format.
  -	</dd>
  -      </dl>
  -
  -</section>
  +    </section>
   
   </body>
   </document>
  
  
  
  1.11.2.1  +11 -15    logging-log4j/src/xdocs/history.xml
  
  Index: history.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/history.xml,v
  retrieving revision 1.11
  retrieving revision 1.11.2.1
  diff -u -r1.11 -r1.11.2.1
  --- history.xml	2 Apr 2002 09:07:35 -0000	1.11
  +++ history.xml	6 May 2005 05:32:36 -0000	1.11.2.1
  @@ -17,20 +17,19 @@
         </p>
   
         <p>The project's official URL is <a
  -	  href="http://jakarta.apache.org/log4j">http://jakarta.apache.org/log4j</a>.
  +	  href="http://logging.apache.org/log4j">http://logging.apache.org/log4j</a>.
         </p>
   
         <p>Many thanks to all the log4j users who keep sending us input
  -	and sometimes even praise for our collective effort. The first
  -	ancestor of log4j was written for the E.U. sponsored <a
  -	href="http://www.semper.org">SEMPER</a> project.  N. Asokan,
  -	Ceki G&#252;lc&#252; and Michael Steiner came up with the idea
  -	of hierarchical loggers back in 1996. Their idea is still
  -	at the heart of log4j. The package was considerably improved
  -	over the years at the <a
  -	href="http://www.zurich.ibm.com"><b>IBM Zurich Research
  -	Laboratory</b></a>. However, log4j is no longer associated nor
  -	supported by IBM.
  +      and sometimes even praise for our collective effort. The first
  +      ancestor of log4j was written for the E.U. sponsored <a
  +      href="http://www.semper.org">SEMPER</a> project.  N. Asokan,
  +      Ceki G&#252;lc&#252; and Michael Steiner came up with the idea
  +      of hierarchical loggers back in 1996. Their idea is still at the
  +      heart of log4j. The package was considerably improved over the
  +      years at the <a href="http://www.zurich.ibm.com">IBM Zurich
  +      Research Laboratory</a>. However, log4j is no longer associated
  +      nor supported by IBM.
         </p>
   
         <p>Special thanks to M. Niksch from ZRL for his assistance on
  @@ -39,10 +38,7 @@
   	helpful in easing the move to Apache.
         </p>
   
  -      <p>The log4j logo was designed and kindly donated by <a
  -	  href="http://www.cyberlab.ch"><IMG
  -	  src="images/cyberlab15.gif" ALT="Cyberlab S.A."
  -	  ALIGN="abscenter"/></a> of Switzerland.
  +      <p>The log4j logo was designed and kindly donated by Cyberlab SA of Switzerland.
         </p> 
   
       </section>
  
  
  
  1.8.2.2   +1 -1      logging-log4j/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/index.xml,v
  retrieving revision 1.8.2.1
  retrieving revision 1.8.2.2
  diff -u -r1.8.2.1 -r1.8.2.2
  --- index.xml	12 Jun 2002 21:31:35 -0000	1.8.2.1
  +++ index.xml	6 May 2005 05:32:36 -0000	1.8.2.2
  @@ -56,7 +56,7 @@
         <p>On an AMD Duron clocked at 800Mhz running JDK 1.3.1, it costs
   	about 5 nanoseconds to determine if a logging statement should
   	be logged or not. Actual logging is also quite fast, ranging
  -	from 21 microseconds microseconds using the SimpleLayout, 37
  +	from 21 microseconds using the SimpleLayout, 37
   	microseconds using the TTCCLayout.  The performance of the
   	PatternLayout is almost as good as the dedicated layouts,
   	except that it is much more flexible.</p>
  
  
  
  1.7.2.2   +46 -189   logging-log4j/src/xdocs/plan.xml
  
  Index: plan.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/plan.xml,v
  retrieving revision 1.7.2.1
  retrieving revision 1.7.2.2
  diff -u -r1.7.2.1 -r1.7.2.2
  --- plan.xml	12 Jun 2002 21:31:35 -0000	1.7.2.1
  +++ plan.xml	6 May 2005 05:32:36 -0000	1.7.2.2
  @@ -11,8 +11,8 @@
       <section name="Plan? What plan?">
   
         <p>The following paragragh was adapted from the <a
  -	  href="http://jakarta.apache.org/cactus/todo.html">Cactus
  -	  project's roadmap</a> with the author's permission.
  +      href="http://jakarta.apache.org/cactus/">Cactus</a> project's
  +      roadmap with the author's permission.
         </p>
         
         <p>Our users keep inventing better ways and adding new
  @@ -44,7 +44,7 @@
   	reliable product.
         </p>
         
  -      <table border="1" cellpadding="3" cellspacing="2">
  +      <table class="ls" cellpadding="3" cellspacing="2">
   	
   	<tr>
   	  <th>Label</th>
  @@ -63,8 +63,8 @@
   	      as early is possible.  It is strongly recommended to add
   	      a new test case with each new feature or component.</p>
   
  -	    <p>Existing <em>Perl</em> language based test cases are
  -	      gradually being migrated to junit (all-Java)based test
  +	    <p>Existing <em>Perl</em> language based test cases have been 
  +			migrated to junit (all-Java)based test
   	      cases.  The new tests are placed under the
   	      <code>tests/</code> directory.  It should be thus
   	      possible for participants in the project to understand
  @@ -91,14 +91,13 @@
   	      are configured separately.
   	    </p>
   
  -	    <p>The support for extensible configuration files will be
  -	    based on the code in commons-digester authored by Craig
  -	    McClanahan and Scott Sanders. They graciously granted
  -	    permission for the modification of their code and its
  -	    inclusion in log4j.</p>	      
  +	    <p>The new JoranConfigurator being created by Ceki will be based on
  +	    a new 'module' know as Joran, which can convert XML files into other objects based
  +	    on rules.  You can read more abouth Joran <b><u><a href="http://www.qos.ch/logging/JoranConfigurator.html">here</a></u></b>
  +	    </p>	      
   	  </td>
   	  <td>Ceki</td>	  
  -	  <td>design board</td>
  +	  <td>Significantly progressed</td>
   	</tr>
   
   	<tr>
  @@ -133,20 +132,35 @@
   	  <td>?</td>	  
   	  <td>vaporware</td>
   	</tr>
  +	<tr>
  +	  <td>Plugins/Receivers</td>
  +	  
  +	  <td>
  +	    <p>A Plugin framework has been designed and implemented.</p>
  +	    <p>All of the currently developed plugins are "Receivers", which can be thought of as the reverse of an appender; something
  +	    that <b>accepts</b> LoggingEvents from some external source.
  +	    </p>
  +	    <p>This has proven particulaly useful with the log4j ports, with the addition of the XML-based Receivers able to accept
  +	    LoggingEvents generated from other languages (see "Overture to other programming languages" below)
  +	    </p>
  +
  +	  </td>
  +	  <td>All</td>	  
  +	  <td>Significantly progressed</td>
  +	</tr>
   
   	<tr>
   	  <td>Improvements to Chainsaw</td>
   	  
   	  <td>
  -	    <p>Visualisation and dynamic filtering of logging event is
  -	      bound to be a very important area of activity in the
  -	      future. A number of important improvements to chainsaw
  -	      have been suggested.
  +	    <p><a href="chainsaw.html">Chainsaw v2</a> development has now progressed to the point where the main developers of it
  +	    and many other members of the logging community are using it daily.  It's still pre-alpha but only
  +	    because we keep thinking up things to add. 
   	    </p>
   	    
   	  </td>
  -	  <td>Oliver Burn</td>	  
  -	  <td>under discusison</td>
  +	  <td>Scott Deboy and Paul Smith</td>	  
  +	  <td>Significantly progressed </td>
   	</tr>
   
   	<tr>
  @@ -157,19 +171,24 @@
   	  extensions to XML configuration language mentioned
   	  above.</td>
   
  -	  <td>?</td> 
  -	  <td>not started</td>
  +	  <td>Ceki</td> 
  +	  <td>Completed, still testing</td>
   	</tr>
   	
   	<tr>
   	  <td>Overture to other programming languages</td>
   
  -	  <td>It is higly desriable to allow log4j ports in other languages 
  -	    to access log4j services in a language independent way. 
  -	  </td>
  +	  <td><p>It is higly desriable to allow log4j ports in other languages 
  +	    to access log4j services in a language independent way. </p>
  +	  
  +	  <p>The use of a standard XML format to represent a LoggingEvent has been established and many of the related logging projects from 
  +	  non-Java languages have begun to support it.   In fact, a number of the log4j ports have volunteered to join Apache!</p>
  +	  
  +	  <p>Scott Deboy has completed work to create a fex XML-based Receiver
  +	  classes that can accept logging events from an external source, and 'import' them into the local log4j environment.  </p> </td> 
   
  -	  <td>?</td> 
  -	  <td>not started</td>
  +	  <td>Ceki, Scott Deboy</td>
  +	  <td>Significantly Progressed (if not completed)</td>
   	</tr>
   
   	<tr>
  @@ -189,8 +208,8 @@
   	    scripts.
   	    </p>
   	  </td>
  -	  <td>Kevin Steppe</td>	  
  -	  <td>not started</td>
  +	  <td>Ceki</td>	  
  +	  <td>Significantly Progressed</td>
   	</tr>
   
   
  @@ -232,169 +251,7 @@
   	</tr>
         </table>
       </section>
  -      
  -      
  -      
  -    <section name="Workplan for log4j 1.2">
  -      <p>
  -	Here is workplan for the 1.2 release.
  -      </p>
  -      
  -      <table border="1" cellpadding="3" cellspacing="2">
  -	    
  -	<tr>
  -	  <th>Label</th>
  -	  <th>Comment</th>
  -	  <th>Volunteer</th>
  -	  <th>Status</th>
  -	</tr>
  -	
  -	<tr bgcolor="DDDDDD">
  -	  <td>More test cases</td>
  -	  
  -	  <td>We need more automated test cases to catch bugs as early
  -	    is possible.It is highly recommended to add a new test case
  -	    with each new feature or component.</td>
  -	  
  -	  <td>All committers</td>
  -	  <td>ongoing effort</td>	  
  -	</tr>
  -
  -
  -	<tr>
  -	  <td>Removal of deprecated methods</td>
  -	    
  -	  <td>Deprecated <code>setOption</code> and <code>getOption</code>
  -	    methods in appender and layouts should be removed.</td>
  -
  -	  <td>Ceki</td>
  -	  <td>done</td>
  -	</tr>
  -	
  -	<tr bgcolor="DDDDDD">
  -	  <td>JDBCAppender</td>
  -	  
  -	  <td>
  -	    <p>We currently have two competing JDBCAppenders: one by
  -	    Thomas Fenner and the other by Kevin Steppe.</p>
  -
  -	    <p>Kevin Steppe stood up and did it.</p>	    
  -	    </td>
  -	  
  -	  <td>Kevin Steppe</td>
  -	  
  -	  <td>done</td>
  -	</tr>
  -	
  -	<tr>
  -	  <td>Log4j in applets</td>
  -	  
  -	  <td>In order to minimize network traffic, the size of log4j-core.jar
  -	    needs to be reduced to at most 50KB.
  -	    
  -	    <p>Log4jME has been released. It's less than 20KB.</p>
  -	  </td>
  -	  
  -	  <td>Ceki</td>
  -	  <td>done</td>
  -	</tr>
  -	
  -	<tr  bgcolor="DDDDDD">
  -	  <td>Improved documentation</td>
  -	  
  -	  <td>Log4j documentation needs to be enhanced with configuration
  -	    examples and much more hand-holding.</td>
  -	  
  -	  <td>Ceki</td>
  -	  
  -	  <td>ongoing effort</td>
  -	  
  -	</tr>
  -	
  -	<tr>
  -	  <td valign="top">Mapped Diagnostic Contexts</td>
  -	  
  -	  <td>Mapped Diagnostic Contexts are similar to the NDC
  -	    except that the MDC is a string to string map instead of
  -	    a stack that the user sets when entering a special
  -	    context. The <code>PatternLayout</code> has to be
  -	    enhanced to support this by extending the %x pattern to
  -	    accept an argument.  Here is an example:
  -	    
  -	    <pre>
  -    ConversionPattern=3D%d %p %c %x{server} %x{host} - %m%n
  -	    </pre>
  -	    
  -	    User code:
  -	    <pre>
  -    {
  -       MDC.put("server", "totoServer");
  -       MDC.put("host", "someHost");
  -	      
  -       logger.debug("Hello");
  -	      
  -    }
  -</pre>
  -      will print:
  -      <pre>2000-01-24 10:00:00,000 DEBUG totoServer someHost - Hello</pre>
  -
  -	    <p>To make MDCs truly user friendly
  -	      <code>ThreadLocal</code> variables are required. This
  -	      will allow the MDC to be inherited by child
  -	      threads. <code>ThreadLocal</code> are only supported
  -	      under JDK 1.2 and above. In JDK 1.1, the MDC will not
  -	      work but won't harm the user application either.</p>
  -	      </td> 
  -	  <td>Ceki</td> 
  -	  <td>done</td>
  -	</tr>
  -
  -	<tr bgcolor="DDDDDD">
  -	  <td>Enhanced variable substitution support in DOMConfigurator</td>
  -	  <td></td>
  -	  
  -	  <td>Ceki</td>
  -	  <td>done</td>	  
  -	</tr>
  -	    
  -	<tr>
  -	  <td>FallbackErrorHandler</td>
  -	  
  -	  <td>The FallbackErrorHandler implements the ErrorHandler
  -	    interface such that a secondary appender may be
  -	    specified. This secondary appender takes over if the primary
  -	    appender fails for whatever reason.
  -	    
  -	    <p>The DOMConfigurator needs to be extended to support the
  -	      FallbackErrorHandler</p>
  -	    
  -	  </td>
  -	  <td>Ceki</td>
  -	  <td>implemented, requires further testing</td>
  -	</tr>
  -	
  -	
  -	<tr>
  -	  <td>Ensure backward compatibility of LoggingEvent
  -	  objects</td> 
  -	  
  -	  <td>To avoid deployment problems we must ensure that
  -	  LoggingEvent objects are compatible between 1.2 and 1.1.3.
  -
  -	    <p>Robert Bushman has proposed a very innovative way for
  -	    solving this problem. See <a
  -	    href="http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg01397.html">
  -	    http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg01397.html</a>
  -	    for further details.
  -	    </p>
  -	  </td>
  -	  
  -	  <td>Ceki</td>
  -	  <td>implemented, manually tested, requires automated test cases</td>
  -	</tr>
  -      </table>
  -    </section>
  -
  +     
     </body>
   
   </document>
  
  
  
  No                   revision
  No                   revision
  1.11.2.2  +11 -11    logging-log4j/src/xdocs/stylesheets/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/stylesheets/project.xml,v
  retrieving revision 1.11.2.1
  retrieving revision 1.11.2.2
  diff -u -r1.11.2.1 -r1.11.2.2
  --- project.xml	19 Feb 2003 13:37:36 -0000	1.11.2.1
  +++ project.xml	6 May 2005 05:32:36 -0000	1.11.2.2
  @@ -1,29 +1,29 @@
  -<?xml version="1.0" encoding="ISO-8859-1"?>
  -<project name="Jakarta Site"
  -        href="http://jakarta.apache.org/">
  +<?xml version="1.0" encoding="UTF-8"?>
  +<project name="Logging Services Log4j"
  +         href="http://logging.apache.org/log4j/docs/">
   
     <title>Log4j project</title>
     <logo href="images/logo.jpg">The log4j project</logo>
     
     <body>
  -    
  +      
       <menu name="Log4j Project">
         <item name="Introduction"   href="/index.html"/>
         <item name="Download"       href="/download.html"/>
         <item name="Documentation"  href="/documentation.html"/>
  +      <item name="Chainsaw"       href="/chainsaw.html"/>
         <item name="Plan"           href="/plan.html"/>
  -      <item name="Wiki"           href="http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages"/>
  +      <item name="Wiki"           href="http://wiki.apache.org/logging-log4j/Log4JProjectPages"/>
         <item name="Contact us"     href="/contactUs.html"/>
         <item name="Contributors"   href="/contributors.html"/>
         <item name="History"        href="/history.html"/>
       </menu>
   
  -    <menu name="Jakarta (parent project)">
  -      <item name="Home page" href="http://jakarta.apache.org/"/>
  -      <item name="News" href="http://jakarta.apache.org/site/news.html"/>
  -      <item name="Mission" href="http://jakarta.apache.org/site/mission.html"/>
  -      <item name="Guidelines" href="http://jakarta.apache.org/site/guidelines.html"/>
  -      <item name="FAQs" href="http://jakarta.apache.org/site/faqs.html"/>
  +    <menu name="Logging Services">
  +      <item name="Home page" href="http://logging.apache.org/"/>
  +      <item name="News" href="http://logging.apache.org/site/news.html"/>
  +      <item name="Mission" href="http://logging.apache.org/site/mission-statement.html"/>
  +      <item name="Guidelines" href="http://logging.apache.org/site/bylaws.html"/>
       </menu>
   
       <menu name="Translations">
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message