It is now also possible to contribute to the argouml projects through Gerrit. This also means that you will be using git instead of subversion so it is also an option for those that prefer git. This approach has some pros and cons.
Here is a short introduction on how to do it:
Register on the Gerrit server and create your Gerrit user, set-up your email, register your public ssh-key with this user. (One time only.)
Clone the git repository git clone ssh://email@example.com:29418/project project, and cd project. (One time per machine you are working on. This takes more than 3 minutes and uses 320Meg for the main argouml project.). For more work using the same machine, you can pull down updates using git pull and git rebase origin/trunk.
Create a local git branch for your work and switch to it git branch work, git checkout work.
- Do your work.
Run the tests (mvn test, mvn exec:java, ...)
Check into your git repository using a single commit git add ..., git commit -m'Message' if needed followed by a sequence of commit amends git commit --amend.
Push your Patch Set to the Gerrit server for review git push origin HEAD:refs/for/trunk. This will fail and suggest a Change-Id if you havn't provided on.
- After your commit, you will get mails from the Gerrit server with information on the Continuous Integration job and other review comments. Monitor the Gerrit server to take part in any discussion of your changes.
If you need to push an updated Patch Set to replace the previous Patch Set commit using git commit --amend and push again git push origin HEAD:refs/for/trunk. This relies on the Change-Id in the commit message to identify the change. The Gerrit server will pick up on the Change-Id and treat this as a replacement Patch Set.
- When a Gerrit Approver has approved your change, it is automatically checked into the subversion repository.
Syntax of commit message