Quick Links:

Releases | Mailing Lists | Source Control | Issue Tracker | Regression Tests

Source Code Control


This project uses Git to manage its source code. Instructions on Git use can be found at http://www.git-scm.com/book/en/v2.

Web Access

The following is a link to the online source repository.


Repository access

To obtain a copy of the current git “HEAD”, use the “git clone” command

$ git clone https://github.com/JikesRVM/JikesRVM.git jikesrvm

or fork the repository on GitHub.

Committers should clone the repository via SSH, using

$ git clone  git@github.com:JikesRVM/JikesRVM.git jikesrvm

Access through a proxy

TODO this section needs to be rewritten for Git. Please help.

Write Permission

To commit changes to the repository, execute the following command to commit your changes.

$ git commit -m “A message”

Unlike Subversion, this only creates a local copy of the changes. To push this back to the public repository,

$ git push

which uses your GitHub SSH key for authentication.

Commit messages

Please write a commit message that describes the purpose of the change. If you are committing code to fix a JIRA issue please include the identifier (i.e. RVM-53) in the commit message. If you are committing code supplied by another individual please indicate the individual.

Commit content

Please keep commits as focused as possible. Separate out functional and non functional changes into separate commits. (i.e. Code formatting changes should appear in different commits from feature modification commits.)

Historical repositories

The historical Subversion repository can be browsed via the Sourceforge web fronted. Note that the repository has a non-standard structure:

The code from the Subversion repository (except for the admin scripts) is mirrored at GitHub. Look for the repositories whose name starts with mirror-historical-svn.