Great you want to contribute!
It’s really simple. Well. There are some rules that you should follow:
The process is mostly automated and convenient.
- Make sure you are following the code style below.
- Make sure your feature is well tested.
- Make sure your feature is well documented (Javadoc).
- Make sure there is documentation for your feature at ninja-core/src/site/markdown.
- Make sure your feature runs inside ninja-integration-test
or ninja-servlet-jpa-blog-integration-test if you wrote a feature related to JPA.
- Add your changes to changelog.md and your name to team.md.
Sign the contributor agreement (electronically) and
send us a pull request to become a happy member of the Ninja family :)
- Default Sun Java / Eclipse code style (a default config for eclipse can be found at the project root eclipse-ninja-format.xml.
- If you change only tiny things only reformat stuff you actually changed. Otherwise reviewing is really hard.
- We use spaces / 4 spaces as a tab in all files (java, xml…).
- Files in git repo should have unix (LF) file endings. We are using the .gitattributes file to handle that for you.
- All files are UTF-8.
Making a Ninja release
- Make sure you are using http://semver.org/ for versioning.
- Make sure changelog.md is updated
- Make sure upgrade-guide top version is updated
- Make sure the archetypes are up-to-date (Ninja version must match release version)
- Make sure the archetypes version in docu (JPA + getting_started) matches release version
2) Release to central maven repo
3) Publish website
- git checkout TAG
- cd ninja-core
- mvn site site:deploy
And back to develop: