Attached the ZIP file with the source code.

The easiest way to get the diff from HG is using 'hg diff -g > mydiff.patch' in the project root

Hello,

For some reason hg stopped working on my computer.

The changes though, is basically inside src. Delete the "shared" folder and unzip the attached ZIP (btrace-maven.zip) inside the src folder. This should lead the following structure under "src":

btrace-agent
btrace-boot
btrace-client
pom.xml
solaris
test

I cloned the Mavenized Core, and had some initial trouble when trying to build with maven.

As I am on a Mac, I dont have a "tools.jar" file at all in my JVM. Apple ships a "classes.jar" that contains the contents from tools.jar as well. Im not sure maven is able to auto-detect the OS, but in order to only have to change the path to classes.jar once, I added a dependencyManagement tag inside the main pom.xml. That way the sub-poms dont have to specify a version, or a path to the jar file.

Also, for some reason, I had to build some of the sub-project manually before the build of the parent pom.xml worked. Im not too sure why that might be.

I am attaching a diff file for the changes I made to the poms.

Hi,
I've slightly modified the patch to be OS sensitive. Could you (anyone owning a mac) try it out?

I will have a look at it this evening.

I tried out the patch today, and it works fine on my machine (OS X 10.6.6, Java build 1.6.0_22-b04-307-10M3261, which is Java for Mac OS X 10.6 Update 3, not the newest Update 4).

Hello,

Trying out a clean clone of the repo (to verify BTRACE-63), I also needed to add the following to the main pom.xml inside the btrace-folder, as my compiler tried to compile with a Java 1.3 complancy for some reason.

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                    <encoding>ISO-8859-1</encoding>
                </configuration>
            </plugin>

Other than that, everything seems to be working as its supposed to! How far off the main repo is the mavenized repo ?

I've applied the proposed change along with some other improvements - http://kenai.com/projects/btrace/sources/core-maven/revision/18.

In fact, the mavenized repo is now ahead of the main repo. Thanks to rather big structural differences between those 2 repos I was commiting fixes and features to the mavenized one only as I hope it will be the primary repo soon.

That sounds very nice indeed! I'm switching to the maven-repo for my continued work on EurekaJ, and I will submit a new diff file for BTRACE-55 as well that works with the mavenized core.