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.mvn verify to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
Every archetype module is tested by its maven-archetype:integration-test goal, which mvn verify runs. Each directory src/test/resources/projects/<name> is one test; the Testing Archetypes guide describes its files (archetype.properties, goal.txt, reference/, verify.groovy) and how the goal compares the generated project with reference/.
To test one archetype, run mvn -B verify -pl maven-archetype-quickstart. Add -T2 to build modules in parallel; the archetype plugin is not marked thread-safe, so Maven warns about it. The generated projects, with their build.log, stay in <module>/target/test-classes/projects/<name>/project. Use -Darchetype.test.skip=true to package the archetypes without running the tests.
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.