Contributing to Apache Maven SCM
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:
git diff --check
before committing.
[SCM-XXX] - Subject of the JIRA Ticket
Optional supplemental description.
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.
Update your JIRA ticket and include a link to the pull request in the ticket.
If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always
necessary to create a new ticket in JIRA. In this case, it is appropriate to
start the first line of a commit with '(doc)' instead of a ticket number.
Contributing patches
Apache Maven scm JIRA project page
Contributor License Agreement
General GitHub documentation
GitHub pull request documentation
Apache Maven Twitter Account
#Maven IRC channel on freenode.org