You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by ce...@apache.org on 2002/02/11 04:23:08 UTC
cvs commit: jakarta-log4j/src/xdocs download.xml
ceki 02/02/10 19:23:08
Modified: . INSTALL build.xml
docs HISTORY download.html
src/java/org/apache/log4j Category.java
src/xdocs download.xml
Log:
Relase 1.2beta1
Revision Changes Path
1.16 +31 -16 jakarta-log4j/INSTALL
Index: INSTALL
===================================================================
RCS file: /home/cvs/jakarta-log4j/INSTALL,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- INSTALL 19 Dec 2001 20:48:30 -0000 1.15
+++ INSTALL 11 Feb 2002 03:23:07 -0000 1.16
@@ -8,14 +8,34 @@
2) Assuming you chose to extract the distribution in to the
PATH_OF_YOUR_CHOICE, untarring the distribution file should create
a jakarta-log4j-VERSION directory, where VERSION is the log4j
- version number, under PATH_OF_YOUR_CHOICE.
+ 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 PATH_OF_YOUR_CHOICE\jakarta-log4j-VERSION\dist\classes to the CLASSPATH
- variable.
+3) Add $LOG4J_HOME/dist/lib/log4j-1.2.jar to your CLASSPATH.
-4) You can now test your installation. To do this issue the command:
+4) You can now test your installation by first compiling the following
+ simple program.
- java org.apache.log4j.test.Hello
+ import org.apache.log4j.Logger;
+ import org.apache.log4j.BasicConfigurator;
+
+ public class Hello {
+
+ static Logger logger = Logger.getLogger(Hello.class);
+
+ public
+ static
+ void main(String argv[]) {
+ BasicConfigurator.configure();
+ logger.debug("Hello world.");
+ logger.info("What a beatiful day.");
+ }
+ }
+
+
+ After compilation, try it out by issuing the command
+
+ java Hello
You should see log statements appearing on the console.
@@ -27,12 +47,11 @@
=========
The log4j distribution comes with one jar file: log4j-VERSION.jar
-under the PATH_OF_YOUR_CHOICE/jakarta-log4j-VERSION/dist/lib/
-directory.
+under the $LOG4J_HOME/dist/lib/ directory.
This jar file contains all the class files of the log4j project,
-except classes from the org.apache.log4j.examples and
-org.apache.log4j.performance packages.
+except classes from the "examples" and "org.apache.log4j.performance"
+packages.
==================
log4j dependencies
@@ -99,12 +118,8 @@
requires a build file called build.xml which is part of this
distribution.
-Log4j is shipped with ant-1.4.jar file under the build/lib/ directory.
-
In case of problems send an e-mail note to
log4j-user@jakarta.apache.org. Please do not directly e-mail any of
-the log4j developers. The answer to your question might be beneficial
-to other users. Closed interaction with developers eliminates the
-advantages of having mailing lists where a large number of
-knowledgeable people lurk.
-
+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.
1.16 +6 -6 jakarta-log4j/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/build.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- build.xml 8 Feb 2002 12:54:16 -0000 1.15
+++ build.xml 11 Feb 2002 03:23:07 -0000 1.16
@@ -14,7 +14,7 @@
<!-- prefixed with "env". -->
<property environment="env"/>
- <property name="version" value="1.2alpha8"/>
+ <property name="version" value="1.2beta1"/>
<!-- The base directory relative to which most targets are built -->
<property name="base" value="."/>
@@ -72,7 +72,9 @@
jar - build log4j-core and log4j jar files
- dist - will create a complete distribution in dist/
+ dist - will create a complete distribution in dist/
+ Setting the env variable NO_JAVADOC will build the distribution
+ with running the javadoc target.
</echo>
</target>
@@ -293,7 +295,7 @@
doctitle="log4j version ${version}<br>API Specification"
windowtitle="Log4j Version ${version}"
header="<b>Log4j ${version}</b>"
- bottom="Please <a href=http://lists.sourceforge.net/mailman/listinfo/log4j-announce><b>notify me</b></a> about new log4j releases. <hr>">
+ bottom="Copyright 2000-2002 Apache Software Foundation.">
<link offline="true"
href="http://java.sun.com/products/jdk/1.2/docs/api"
@@ -352,9 +354,6 @@
build/*,
build.bat, build.sh,
build.xml,
- build/lib/ant-1.4.jar,
- build/lib/jaxp-1.1.jar,
- build/lib/crimson-1.1.jar,
manifest.mf,
INSTALL,
LICENSE.APL,
@@ -368,6 +367,7 @@
**/*.bak, **/goEnv.bat,
**/Makefile, **/goEnv.bat,
docs/pub-support/*,
+ src/java/org/apache/log4j/test/**/*,
src/java/org/apache/log4j/test/serialization/T/*.jar,
src/java/org/apache/log4j/test/serialization/T/compile,
src/java/org/apache/log4j/test/serialization/**/*.class,
1.81 +8 -2 jakarta-log4j/docs/HISTORY
Index: HISTORY
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/HISTORY,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- HISTORY 8 Feb 2002 12:54:16 -0000 1.80
+++ HISTORY 11 Feb 2002 03:23:08 -0000 1.81
@@ -7,9 +7,15 @@
??, 2002
- - Release of version 1.2 (ALPHA)
+ - Release of version 1.2
- (alpha8)
+ (beta1)
+
+ - Source code written for log4j 1.1.3.jar will compile fine with
+ log4j 1.2. However, code compiled with log4j-1.1.3.jar will
+ not run with log4j-1.2.jar. This is because the java compiler is
+ forgiving on the return type of methods whereas the java runtime is
+ not. [?]
- Log4j 1.2 is now backward compatible in serialization of
LoggingEvents. For example, a 1.1.3 SocketAppedner can write to 1.2
1.46 +24 -29 jakarta-log4j/docs/download.html
Index: download.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/download.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- download.html 8 Feb 2002 13:23:29 -0000 1.45
+++ download.html 11 Feb 2002 03:23:08 -0000 1.46
@@ -14,9 +14,6 @@
<meta name="author" value="Ceki Gulcu">
<meta name="email" value="ceki@apache.org">
-
- <meta name="keywords" content="java, logging, tracing, component, framework, API, log4j" />
-
<title>Log4j project - Download</title>
</head>
@@ -102,22 +99,24 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="log4j version 1.2 alpha7"><strong>log4j version 1.2 alpha7</strong></a>
+ <a name="log4j version 1.2 beta1"><strong>log4j version 1.2 beta1</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
- <p>An alpha version of log4j 1.2 is now available in in <a href="../jakarta-log4j-1.2alpha7.tar.gz"><b>TAR.GZ</b></a>
- format or in <a href="../jakarta-log4j-1.2alpha7.zip"><b>ZIP</b></a> format.
+ <p>An alpha version of log4j 1.2 is now available in in <a href="../jakarta-log4j-1.2beta1.tar.gz"><b>TAR.GZ</b></a>
+ format or in <a href="../jakarta-log4j-1.2beta1.zip"><b>ZIP</b></a> format.
</p>
- <p>Log4j version 1.2 is still in alpha stage. It is not
- feature-complete, still requries fair amount of testing, nor
- is the documentation up to date. We have gone to great lengths
- to ensure that version 1.2 is backward compatible with earlier
- versions. However, some previously deprecated APIs are now
- removed. Moreover, users who have written sub-classes of
- Category will need to modify their code. See the HISTORY file
- for more details.
+ <p>Log4j version 1.2 is not feature-complete, nor is the
+ documentation up to date. Some previously deprecated APIs are
+ now removed. Moreover, users who have written sub-classes of
+ Category will need to modify their code. We have gone to great
+ lengths to ensure that version 1.2 is backward compatible with
+ earlier versions. <b>Client source code writen for log4j 1.1.3
+ will compile without any problems using log4j version
+ 1.2. Unfortunately however, the resulting class files are not
+ compatible. In other words, class files compiled will log4j
+ 1.1.3 will not run with log4j version 1.2.</b>
</p>
</blockquote>
</p>
@@ -139,17 +138,19 @@
<dd>Chainsaw is a GUI 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.
- </dd>
+ and displays them in a table. Chainsaw also supports loading
+ events from files in the XMLLayout format.
+ </dd>
<dt><a href="http://qos.ch/"><b>log4j<em>ME</em></b></a></dt>
- <dd>Log4j<em>ME</em>, or log4j MicroEdition, is based on the same
- code as log4j. However, as the name indicates the micro-edition is
- much smaller. It offers the same client interface such that code
- compiled for log4jME is 100% 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.
+ <dd>Log4j<em>ME</em>, or log4j MicroEdition, is based on the
+ same code as log4j. However, as the name indicates the
+ micro-edition is much smaller. It offers the same client
+ interface such that code compiled for log4jME is 100%
+ 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.
</dd>
<dt><a href="http://traxel.com/lumbermill/"><b>Lumbermill</b></a></dt>
@@ -275,12 +276,6 @@
</body>
</html>
<!-- end the processing -->
-
-
-
-
-
-
1.59 +3 -0 jakarta-log4j/src/java/org/apache/log4j/Category.java
Index: Category.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/java/org/apache/log4j/Category.java,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- Category.java 10 Jan 2002 08:44:17 -0000 1.58
+++ Category.java 11 Feb 2002 03:23:08 -0000 1.59
@@ -89,6 +89,7 @@
// RootCategory(Level.DEBUG));
+ static int nooptimize;
/**
The name of this category.
@@ -517,6 +518,7 @@
public
static
Logger getInstance(String name) {
+ nooptimize++;
return LogManager.getLogger(name);
}
@@ -533,6 +535,7 @@
public
static
Logger getInstance(Class clazz) {
+ nooptimize++;
return LogManager.getLogger(clazz);
}
1.44 +24 -20 jakarta-log4j/src/xdocs/download.xml
Index: download.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/xdocs/download.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- download.xml 8 Feb 2002 13:23:30 -0000 1.43
+++ download.xml 11 Feb 2002 03:23:08 -0000 1.44
@@ -58,22 +58,24 @@
</section>
- <section name="log4j version 1.2 alpha7">
+ <section name="log4j version 1.2 beta1">
<p>An alpha version of log4j 1.2 is now available in in <a
- href="../jakarta-log4j-1.2alpha7.tar.gz"><b>TAR.GZ</b></a>
+ href="../jakarta-log4j-1.2beta1.tar.gz"><b>TAR.GZ</b></a>
format or in <a
- href="../jakarta-log4j-1.2alpha7.zip"><b>ZIP</b></a> format.
+ href="../jakarta-log4j-1.2beta1.zip"><b>ZIP</b></a> format.
</p>
- <p>Log4j version 1.2 is still in alpha stage. It is not
- feature-complete, still requries fair amount of testing, nor
- is the documentation up to date. We have gone to great lengths
- to ensure that version 1.2 is backward compatible with earlier
- versions. However, some previously deprecated APIs are now
- removed. Moreover, users who have written sub-classes of
- Category will need to modify their code. See the HISTORY file
- for more details.
+ <p>Log4j version 1.2 is not feature-complete, nor is the
+ documentation up to date. Some previously deprecated APIs are
+ now removed. Moreover, users who have written sub-classes of
+ Category will need to modify their code. We have gone to great
+ lengths to ensure that version 1.2 is backward compatible with
+ earlier versions. <b>Client source code writen for log4j 1.1.3
+ will compile without any problems using log4j version
+ 1.2. Unfortunately however, the resulting class files are not
+ compatible. In other words, class files compiled will log4j
+ 1.1.3 will not run with log4j version 1.2.</b>
</p>
</section>
@@ -89,17 +91,19 @@
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.
- </dd>
+ and displays them in a table. Chainsaw also supports loading
+ events from files in the XMLLayout format.
+ </dd>
<dt><a href="http://qos.ch/"><b>log4j<em>ME</em></b></a></dt>
- <dd>Log4j<em>ME</em>, or log4j MicroEdition, is based on the same
- code as log4j. However, as the name indicates the micro-edition is
- much smaller. It offers the same client interface such that code
- compiled for log4jME is 100% 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.
+ <dd>Log4j<em>ME</em>, or log4j MicroEdition, is based on the
+ same code as log4j. However, as the name indicates the
+ micro-edition is much smaller. It offers the same client
+ interface such that code compiled for log4jME is 100%
+ 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.
</dd>
<dt><a
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>