JCR is a Web application for performing and managing formal code reviews. Although it has some special logic for reviewing Java projects, it can be used for reviews of any type of source code. JCR manages all stages of the review process (initial project setup, individual review, joint review meeting, post-review tidy-up), but it's mainly there to show diff views of files that have changed and to allow comments to be made on any line of any file marked for review.
| Tags | Software Development Quality Assurance |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Linux Unix |
| Implementation | Python Java |
Recent releases


Changes: The main change in 0.7.0 is support for creating review projects directly from Subversion repositories, without having to upload the code to be reviewed. This is the first of a number of planned version control systems to be supported. This version of JCR also provides some configuration control over code syntax highlighting (by file extension), and fixes some bugs. Changes since version 0.7.0rc1 were limited to a fix for a pre-existing bug and some documentation updates.


Changes: This release adds support for creating review projects directly from Subversion repositories (in addition to the existing ability to upload file sets). It also adds some control of syntax coloring (configured by file extension), and also includes bugfixes.


Changes: The primary focus of this version is to support updates to third party libraries, particularly a bug caused by one of these updates. There is also a more functional makeReviewTarballSvn.sh script, minor enhancements to comment editing and navigation, and the usual bugfixes.


Changes: This version uses AJAX to periodically update the file review page and to toggle the display of project and file notes without having to refresh the page. The file review page now shows file paths before filenames, but this can be toggled. Caching of review files has been made faster, and a number of small bugs have been fixed and minor improvements were made.


Changes: The review file caching introduced in 0.6.5 finally proved to be slow on projects with more than a few review files; the new caching scheme fixes this. If you disabled caching on 0.6.5 to work around this, you should now re-enable it. There have also been some minor enhancements, principally that toggling of project and file note visibility is now mostly handled by Javascript, and therefore does not require the page to be refreshed.