You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by ps...@apache.org on 2003/06/29 23:59:48 UTC
cvs commit: jakarta-log4j-sandbox HOWTOBUILD-CHAINSAW2.txt chainsaw-build.xml build.chainsaw.properties.sample
psmith 2003/06/29 14:59:48
Modified: . HOWTOBUILD-CHAINSAW2.txt chainsaw-build.xml
Removed: . build.chainsaw.properties.sample
Log:
Updates to show that Chainsaw has moved from the Sandbox
into jakarta-log4j module.
Have kept the build file for chainsaw for anyone expecting it, but
all it does now is output a messages that indicates that Chainsaw has
moved.
We can remove it completely in a short time.
Revision Changes Path
1.4 +5 -76 jakarta-log4j-sandbox/HOWTOBUILD-CHAINSAW2.txt
Index: HOWTOBUILD-CHAINSAW2.txt
===================================================================
RCS file: /home/cvs/jakarta-log4j-sandbox/HOWTOBUILD-CHAINSAW2.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- HOWTOBUILD-CHAINSAW2.txt 21 May 2003 06:41:36 -0000 1.3
+++ HOWTOBUILD-CHAINSAW2.txt 29 Jun 2003 21:59:48 -0000 1.4
@@ -1,82 +1,11 @@
HOWTOBUILD-CHAINSAW2.txt
=======================
-This document outlines the steps required to build and run the Sandbox version
-Chainsaw (version 2).
+Chainsaw v2 has moved!
-Comments/Changes/Bugs for this document and build process:
- * Log4j Developers list (log4j-dev@jakarta.apache.org)
+Chainsaw v2 has been moved into the jakarta-log4j module, in line with
+an eventual supported release.
+regards,
-Assumptions
-===========
-* Familiar with Ant, and have it installed (http://ant.apache.org/)
- (requires the 1.5.x series of Ant, including Conditions support)
-
-Step-by-Step to get Chainsaw2 running
-======================================
-
-1. Download the jakarta-log4j-sandbox (you've probably already done this if you're reading
- this...)
-
-2. Copy the build.chainsaw.properties.sample file -> build.chainsaw.properties
-
-3. Edit the build.chainsaw.properties file and modify to suit your needs. In particular
- * Ensure the "Library Path Stuff" section contains correct relative/full paths to the
- relevant libraries (You might need to source these from the 'Net)
-
- * Ensure the log4j.core.jar is set to the relative/full path to an existing log4j core
- jar file. At this point we recommend actually downloading the jakarta-log4j module
- and running the "jar" target to generate the jar (don't
- forget to point the log4j.core.jar property in build.chainsaw.properties to
- this file!)
-
- **** Notes: the intent of the chainsaw-build.xml file is to be able to get it to
- automatically do the external Ant call for you, but for now,
- it's not operational - please provide the log4j-core jar.
-
- * Ensure the log4j.configuration.dir property points to a relevant directory, and
- there is a valid Log4j xml configuration file in there. Also ensure that the
- log4j.configuration property is set to that configuration file name.
-
- **** Notes: See the src/config/log4j-sample.xml for a sample configuration that
- should receive events from Sockets on the standard 4445 port, and funnel
- into Chainsaw2.
-
-4. From the jakarta-log4j-sandbox root directory, type:
-
- ant -f chainsaw-build.xml
-
- This should run all the relevant targets and you should see Chainsaw2, with some in-
- progress documentation! (apoligise for the poor documentation so far...We're working on
- it!)
-
-Once the application you have generating Log4j starts streaming them to an appropriate
-SocketAppender targetted to the IP address of your local machine, you should see
-a new Tab appear (maybe title 'Unknown'). Click on this tab to view your Events!
-
-Notes:
-======
-The chainsaw-build.xml script compiles and updates some of the log4j-core functionality.
-The log4j-core jar that is used (either provided, or built using an automated external Ant
-call) is updated with the changed files to ensure this new version of Chainsaw works.
-
-These changes to the log4-core are currently being reviewed by the Dev community and
-should soon be included in the main jakarta-log4 module in some format shortly (cross
-fingers).
-
-Once these changes have been integrated into the core, we will remove the need for this
-update to an external jar. We're just trying to simulate as much as possible real world
-conditions.
-
-Known Bugs/Issues:
-==================
-
-* The developers have noticed a periodic error in the build process trying to
- update the log4j jar. Specifically you may see an Ant message like:
-
- "Unable to rename old file to temporary file"
-
- This error seems to be periodic, and often goes away simply by re-running the
- build. If you have any thoughts on this process, please contact the
- log4j-dev list
+The Log4j Dev team
\ No newline at end of file
1.11 +6 -128 jakarta-log4j-sandbox/chainsaw-build.xml
Index: chainsaw-build.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j-sandbox/chainsaw-build.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- chainsaw-build.xml 17 Jun 2003 22:03:13 -0000 1.10
+++ chainsaw-build.xml 29 Jun 2003 21:59:48 -0000 1.11
@@ -1,165 +1,43 @@
<!--
=============================================================================
- An ANT script to build the Chainsaw module.
-
- This script requires access to a few Jar's including:
-
- * Log4j.jar (the core Log4j Libraries
- * JAXP
- * Jakarta Reg Exp
- * Jakarata ORO
-
-
- Please look out of the HOWTOBUILD-CHAINSAW2.txt file where you will see
- more documention on using this file
+ THIS BUILD FILE IS NO LONGER IN USE!
+
+ Please see the jakarta-log4j CVS module
+
=============================================================================
-->
<project name="Chainsaw/Logui" basedir="." default="chainsaw2">
- <!-- We load some location specific properties from this file, feel free to modify-->
- <property file="build.chainsaw.properties"/>
-
- <property name="log4j.debug" value="true"/>
- <property name="deprecation" value="on"/>
- <property name="debug" value="on"/>
-
- <!-- The directory where source files are stored. -->
- <property name="java.source.dir" value="src/java"/>
-
- <!-- Destination for compiled files -->
- <property name="javac.dest" value="dist_chainsaw/classes"/>
-
- <property name="log4j-chainsaw.jar" value="log4j-chainsaw2.jar"/>
-
- <property name="jar.dest" value="${basedir}"/>
-
- <!-- Construct compile classpath -->
- <path id="compile.classpath">
- <pathelement location="${jaxp.jaxp.jar}"/>
- <pathelement location="${jaxp.parser.jar}"/>
- <pathelement location="${regexp.oro.jar}"/>
- <pathelement location="${log4j.core.jar}"/>
- </path>
-
<!-- Target to clean up the compiled jar file-->
<target name="clean" depends="init">
- <delete>
- <fileset dir="${jar.dest}">
- <include name="${log4j-chainsaw.jar}"/>
- </fileset>
- </delete>
-
- <delete dir="${javac.dest}"/>
</target>
-
<target name="init" depends="">
- <mkdir dir="${javac.dest}"/>
+ <echo message="Chainsaw v2 has been moved to the jakarta-log4j CVS module, we apologise for the inconvenience"/>
+ <fail message="This build file is no longer in use, please see the jakarta-log4j CVS module."/>
</target>
<target name="compile" depends="init">
- <javac srcdir="${java.source.dir}"
- destdir="${javac.dest}"
- deprecation="${deprecation}"
- debug="${debug}"
- excludes="**/*.html,**/*.jpg,**/servlet/*.java">
- <classpath refid="compile.classpath"/>
- </javac>
-
</target>
<target name="check-env-external-libs" depends="init">
- <condition property="log4j.core.jar.present">
- <and>
- <isset property="log4j.core.jar" />
- <available file="${log4j.core.jar}">
- </available>
- </and>
- </condition>
</target>
<target name="check-env-core-jar" depends="init">
- <condition property="external.libraries.oro.present">
- <and>
- <isset property="regexp.oro.jar" />
- <available file="${regexp.oro.jar}"/>
- </and>
- </condition>
-
- <fail unless="external.libraries.oro.present" message="It appears your are missing the Jakarta ORO package. Please check the build.chainsaw.properties file."/>
</target>
-<!-- Determines if the environment, properties are all in order -->
<target name="check-env" depends="check-env-core-jar,check-env-external-libs">
- <condition property="log4j.either.core.or.rebuild">
- <or>
- <isset property="log4j.core.jar.present" />
- <istrue value="${log4j.core.rebuild}" />
- </or>
- </condition>
- <fail unless="log4j.either.core.or.rebuild" message="Properties Configuration check failed (see build.chainsaw.properties). Either the log4j.core.rebuild property is not true, or you haven't provided a valid log4j.core.jar location property." />
</target>
-<!-- Builds all the code -->
<target name="build" depends="check-env, compile">
- <copy todir="${javac.dest}">
- <fileset dir="${java.source.dir}" >
- <patternset>
- <include name="**/*.dtd"/>
- <include name="**/*.properties"/>
- <include name="**/*.html"/>
- <include name="**/*.jpg"/>
- <include name="**/*.gif"/>
- </patternset>
- </fileset>
- </copy>
-
- <jar jarfile="${jar.dest}/${log4j-chainsaw.jar}" basedir="${javac.dest}"
- includes="**/chainsaw/**">
- </jar>
</target>
-<!-- Ensure that the log4j.core.jar file is updated with some
- subtle changes to the core libraries that are required for Chainsaw2.
-
- These changes are currently under review for inclusion in the log4j-core release.
--->
<target name="update-with-core-changes" depends="init,compile">
- <jar update="true" jarfile="${log4j.core.jar}" basedir="${javac.dest}"
- includes="**/spi/*,**/xml/*,**/net/*,**/helpers/*,**/plugins/*,**/org/apache/log4j/*,**/jdbc/*"
- >
- </jar>
-
</target>
-<!-- Launches the Chainsaw app -->
<target name="chainsaw2" depends="build, update-with-core-changes">
- <!-- Need to fork to avoid problems -->
- <java classname="org.apache.log4j.chainsaw.LogUI" fork="yes">
- <sysproperty key="log4j.configuration" value="${log4j.configuration}" />
- <sysproperty key="log4j.debug" value="${log4j.debug}" />
- <sysproperty key="user.timezone" value="${chainsaw.timezone}" />
-
- <classpath>
- <path refid="compile.classpath"/>
- <pathelement location="${jar.dest}/${log4j-chainsaw.jar}"/>
- <pathelement location="${log4j.configuration.dir}"/>
- </classpath>
- </java>
</target>
-<!-- Launches the Generator app -->
<target name="generator" depends="build">
- <!-- Need to fork to avoid problems -->
- <java classname="org.apache.log4j.chainsaw.Generator" fork="yes">
- <sysproperty key="log4j.configuration" value="log4j-generator.xml" />
- <sysproperty key="log4j.debug" value="${log4j.debug}" />
-
- <classpath>
- <path refid="compile.classpath"/>
- <pathelement location="${jar.dest}/${log4j-chainsaw.jar}"/>
- <pathelement location="${log4j.configuration.dir}"/>
- </classpath>
- </java>
</target>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org