cvs commit: jakarta-log4j/docs HISTORY

ceki        02/05/10 01:00:54

  Modified:    .        INSTALL build.xml
               docs     HISTORY
  Log:
  Cosmetic changes plus an important one: the contents of the dist/classes/org/
  directory is no longer included in the distribution images. This reduces
  the size of the tat.gz and zip files by about 30%.
  
  Revision  Changes    Path
  1.19      +9 -9      jakarta-log4j/INSTALL
  
  Index: INSTALL
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j/INSTALL,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- INSTALL	16 Apr 2002 14:37:32 -0000	1.18
  +++ INSTALL	10 May 2002 08:00:54 -0000	1.19
  @@ -11,7 +11,8 @@
      version number, under PATH_OF_YOUR_CHOICE. We will refer to the
      directory PATH_OF_YOUR_CHOICE/jakarta-log4j-VERSION/ as $LOG4J_HOME/.
   
  -3) Add $LOG4J_HOME/dist/lib/log4j-1.2.jar to your CLASSPATH.
  +3) Assuming you are using log4j version 1.2, add
  +   $LOG4J_HOME/dist/lib/log4j-1.2.jar to your CLASSPATH,
      
   4) You can now test your installation by first compiling the following
      simple program.
  @@ -57,8 +58,7 @@
   log4j dependencies
   ==================
      
  -The log4j distribution comes with pre-compiled classes. Log4j is based
  -on JDK 1.1 with the following additional requirements:
  +Log4j is based on JDK 1.1 with the following additional requirements:
   
       ----------------------------
       Package org.apache.log4j.xml 
  @@ -104,8 +104,8 @@
       -----------------------
   
       Log4j uses the JUnit framework version 3.7 for internal unit
  -    testing.  If you want to compile all log4j source code, then you
  -    will need JUnit. JUnit is available from:
  +    testing.  If you want to compile the source code in the tests/
  +    directory, then you will need JUnit. JUnit is available from:
   
             http://www.junit.org
   
  @@ -121,7 +121,7 @@
   build.properties.sample file.
   
   In case of problems send an e-mail note to
  [email protected].  Please do not directly e-mail any of
  -the log4j developers. The answer to your question might be useful to
  -other users. Moreover, there are many knowledgeable users on the
  -log4j-user mailing lists who can quickly answer your questions.
  [email protected].  Please do not directly e-mail any
  +log4j developers. The answer to your question might be useful to other
  +users. Moreover, there are many knowledgeable users on the log4j-user
  +mailing lists who can quickly answer your questions.
  
  
  
  1.34      +1 -0      jakarta-log4j/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j/build.xml,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- build.xml	30 Apr 2002 15:56:34 -0000	1.33
  +++ build.xml	10 May 2002 08:00:54 -0000	1.34
  @@ -423,6 +423,7 @@
   		          **/*.bak, **/goEnv.bat,
   		          **/Makefile, **/goEnv.bat,
   	                  docs/pub-support/*,
  +                          dist/classes/org/**,
   	                  src/java/org/apache/log4j/test/**/*,	
   			  **/.#*"/>
       </copy>
  
  
  
  1.97      +1 -1      jakarta-log4j/docs/HISTORY
  
  Index: HISTORY
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j/docs/HISTORY,v
  retrieving revision 1.96
  retrieving revision 1.97
  diff -u -r1.96 -r1.97
  --- HISTORY	9 May 2002 20:15:01 -0000	1.96
  +++ HISTORY	10 May 2002 08:00:54 -0000	1.97
  @@ -5,7 +5,7 @@
          client code. 
    [***] Changes requiring important modifications to existing client code.
   
  - April, 2002
  + May, 2002
    
    - Release of version 1.2