You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

There are many ways you can help make ServiceMix a better piece of software - please dive in and help!

Try surf the documentation - if somethings confusing or not clear, let us know. Download the code, try it out, and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?

Want to do some hacking on ServiceMix? Try surfing the our issue tracker for open issues or features that need to be implemented, take ownership of an issue and try to fix it.

If you'd rather a more gentle introduction to working on the ServiceMix project, look at the unit tests cases and help us to improve our test coverage.

Getting In Touch

There are various ways of communicating with the ServiceMix community.

  • visit the Discussion Forum
  • subscribe to the Mailing Lists and take part in any conversations
  • pop by on IRC and say hi
  • add some comments to the wiki(requires a log in)
  • if you use ServiceMix please tell us about it on our Users page

If You Find a Bug or Problem

Please raise a new issue in our issue tracker
If you can create a JUnit test case then your issue is more likely to be resolved quicker.
e.g. take a look at some of the existing unit tests cases

Then we can add your issue to CVS and then we'll know when its really fixed and we can ensure that the problem stays fixed in future releases.

Submitting Patches

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. Create a new JIRA issue fully explaining the situation, including the environments you've test, the JVM you're using and anything else that might be useful to know about the situation
  2. Attach the patch to the issue that you are creating and make sure to tick the 'Patch Attached' checkbox on the issue
  3. 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
  4. 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.

Creating the Patch

Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch:

diff -u Main.java.orig Main.java >> patchfile.txt

or

svn diff Main.java >> patchfile.txt

A Tip For Creating Patches

When creating a patch, making sure the patch filename ends in .txt will allow it to be easily viewed in a browser.

Using the Issue Tracker

Before you can raise an issue in the issue tracker you need to register with it. This is quick & 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.

Why not dive in and try tackle some of our outstanding issues?

type key summary assignee reporter priority status resolution created updated due

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Error rendering macro 'jiraissues'

Macro params are invalid

Becoming a Committer

The first step is contributing to the project; if you want to take that a step forward and become a fellow committer on the project then see the Committer Guide

  • No labels