The build requires that you have jrockit installed and set -Djrockit.home=/path/to/jrockit. However, that is harder said than done now that jrockit no longer seems to be available for download following the acquisition of BEA by Oracle.

AOP trunk has this jrockit dependency as a profile in the build, so you could try copying that. Or you could try doing your work in trunk, as I am releasing 2.1.4 today, which will probably be the last 2.1.x release.

I even succeeded in building the jar needed for my project (jboss-aop.jar)It seems to solve my problems.

Now I would like to create an official patch for this and here is where the trouble starts for me.

I have read loads of information from the above links and think I have to take the following steps:

1) sign a developer contract. (done)2) Get the software to patch (from https://svn/jboss.org/repos/...)3) Make the changes in the software.4) build the software.5) test it.6) create a patch in JIRA.7) upload a jar in JIRA.8) wait for QA to respond.

I'm sure of the first and third step ;-)

So before messing up the complete JBoss development process I would like to know:

Can someone tell me if I'm correct with the above steps or what is missing?

1)I accepted your developer contract thing, but since we have had very few external committers to jboss aop and this process is new, I am unsure about how it works. I will make some enquiries, but the lead of jboss.org is on holiday.

2-5)For testing we do two thingsa) Make sure that the tests in aop/ itself do not fail with your changes, i.e.

cd aop/
ant -f build-tests-jdk50.xml tests

b) Make sure the test does not break the in AS tests Check out jboss application server version 5.1.0.GA and build it

I see I answered the wrong thing for your previous post with the build failure, thinking it was to do with JRockit. The builds should work out of the box for the mentioned branches, if you have any problems building please post them here.

Also build the trunk of aop without my code changes.While testing (build-tests-jdk50.xml tests) the same failures and behavior occurs (Stops responding while compiling) as with testing the Branch_2_1 part.

It all happens before I changed anything.

Just did a svn co ...... , build it with build/build.sh and then aop/build-tests-jdk50.xml tests.(but then the equivalent in eclipse ;-).

<background music of tv series "twilight zone">I now have two processes doing something mysterious.<\background music of tv series "twilight zone">

As I will be on holiday for the next three weeks I will leave it at this and come back to you after my holiday.

You can ignore the Precedence test failures, and we will try to look later. The background for this is that the ordering is influences by the OS the JVM is running on. Our automated test runs are on Linux and Flavia is on Linux. I used to be on Windows, but have been on OS X for a year. Since you're the first Windows user to run these in a long time that is probably that cropping up again.

Same for the XXXXOutOfVmTestCases. They used to work on Windows, but have not been run there for a long time. The issue is looking up the 'java' executable.

However, the annotationoverride test should not take that long, it should only take a few seconds (as should all the tests). If you have not already done so, try quitting and starting it all again. If that does not work, try taking a thread dump (I think it is CTRL-BREAK on Windows).

For your own purposes when getting up to speed, you can disable tests by commenting them out in base-tests.xml.