Index > Community > Contributing

There are many ways you can help make XBean 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 XBean? 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 XBean project, try 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 XBean community.

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 SVN 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 XBean in some way.

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


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 xbean-developers on the issue tracker. To join the group, please let us know on the Mailing Lists letting us know the user name 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?

JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
JIRA Issues Macro: 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