Page History

...

Please raise a new issue in our the JIRA issue tracker
If you can create a JUnit test case then your issue is more likely to be resolved quicker.
e.g. The best way to start is to take a look at some of the existing unit tests cases as examples. Then we can add your issue to CVS and then commit your test case along with your patch to Subversion so that we'll know when that the issue its really fixed and we can ensure that the problem it stays fixed in future releases.

...

We gladly accept patches if you can find ways to improve, tune or fix ServiceMix in some way. To submit a patch, please use the following steps:

1. Build against the trunk to ensure that your code compiles correctly and that your test runs
2. Create a new JIRA issue that fully explaining explains the situation, including the environments you've testtested, the JVM version and vendor you're using and anything else that might be useful to know about the situation
3. Attach the patch to the issue that you are creating and make sure to tick the 'Patch Attached' checkbox on the issue
4. Send an email to the Mailing Lists or Discussion Forums to let people know you've filed an issue and contributed a patch for the issue
5. Please try to also submit tests in the patch. Including tests makes applying the patch much easier and faster. Tests allow a patch to be applied and tested much quicker which results in your issue being fixed faster.

...

Using the Issue Tracker

Before you can raise create an issue in the JIRA issue tracker you need to register an account with it. This is quick & and painless.

If you want to have a go at fixing an issue you need to be in the list of servicemix-developers on the issue tracker. To join the group, please mail the dev@servicemix.codehaus.org mail list with the email address you used to register with the issue tracker and we'll add you to the group.

...