The Fourth Place

I needed to access chainsaw’s library from a project, and determined that this is best done from source rather than downloading the JARs. What if something happens to the chainsaw project?

So I got HEAD from the SVN location below:

http://svn.apache.org/repos/asf/logging/chainsaw/trunk

This returned revision 789818, fwiw.

HOWTOBUILD in that project contained these other source dependencies:

log4j-component – http://svn.apache.org/repos/asf/logging/log4j/companions/component/trunk/
log4j-pattern-layout – http://svn.apache.org/repos/asf/logging/log4j/companions/pattern-layout/trunk/
log4j-receivers – http://svn.apache.org/repos/asf/logging/log4j/companions/receivers/trunk/
log4j-filters – http://svn.apache.org/repos/asf/logging/log4j/companions/filters/trunk/
log4j-zeroconf – http://svn.apache.org/repos/asf/logging/log4j/companions/zeroconf/trunk/

-component, -receivers and -zeroconf were found, there was no evidence of -pattern-layout
or -filters in the public SVN. Therefore the following were downloaded using the commands
Import->Check out Maven projects from SCM feature in Eclipse

JMX was downloaded from here:

http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/download.jsp

and unpacked to here:
/home/simon/Desktop/jmx-1_2_1-bin/

and installed with:

mvn install:install-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/home/simon/Desktop/jmx-1_2_1-bin/lib/jmxtools.jar
mvn install:install-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/home/simon/Desktop/jmx-1_2_1-bin/lib/jmxri.jar

log4j-component built immediately with mvn install. Both of the others had direct
dependencies on artifact “log4j:log4j:jar:1.2.16-SNAPSHOT”

Downloading logj was done the same way. (I had some errors with folders that could not
be renamed , I cleared some guff from the target folder to fix) I downloaded from

https://svn.apache.org/repos/asf/logging/log4j/trunk

and got revision 790113

Building started in the Eclipse IDE and caused issues for mvn install. mvn clean install worked fine for log4j.

Building chainsaw requires a clean build of receivers and chainsaw. Build chainsaw with:

mvn -Dmaven.test.skip=true clean package
mvn -Dmaven.test.skip=true install

or similar, otherwise the tests will fail on you (mildly alarming).

Notes about my set up:

I have Eclipse 3.4.2 with

- Sonatypes Maven Integration for Eclipse 0.9.7.
- Subclipse (from update site  http://subclipse.tigris.org/update_1.4.x)

Once I got going I realised the project need not be included in my Eclipse workspace.