You have found a bug, or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
Make commits of logical units.
Respect the original code style: by using the same codestyle, patches should only highlight the actual difference, not being disturbed by any formatting issues:
git diff --check
before committing.Make sure you have added the necessary tests (JUnit/IT) for your changes.
Run all the tests with mvn -Prun-its verify
to assure nothing else was accidentally broken.
Submit a pull request to the repository in the Apache organization.
If you plan to contribute on a regular basis, please consider filing a contributor license agreement.