JCR free download, JCR download on software download

A web-based tool for performing and managing code reviews, usable for code in any language, but provides some extra features for Java JCR is a free and open source web application for performing and managing formal code reviews. JCR can be used for reviews of any type of source code, although it has some special smarts for reviewing Java projects. JCR has special features to make large-scale reviews not only practical but easy and fast.JCR is intended to assist:· Reviewers. All changes to code are highlighted, and syntax highlighting works for most languages. Code extracts are shown for context when adding comments. If reviewing Java code, references to other classes within the file are clickable, so that you can drill into the detail if required. After review comments have been made, those comments can themselves be reviewed, and the required actions decided on and tracked· Project owners. Review projects are easy to create and configure, and don't require any integration with your source code management (SCM) system· Process bigots. Details of all comments are held in the database, along with any actions required, and whether they've been completed. Status reports can be viewed at any time, and also show how much review activity took place on each file (to make sure they were all reviewed)· Architects and developers. As well as viewing the comments made for a project, it's possible to see details of all review projects and comments for a specified file - good for finding code that would benefit from refactoring. Here are some key features of "JCR": Education: · Code reviews are a great way of pointing out good or bad techniques to other developers (particularly less-experienced ones) and making developers aware of internal or external libraries etc. that can be used instead of resorting to wheel-reinvention. Additionally, they give you an opportunity to discuss some of the issues, to make sure everyone's on the same page. · Oh, and you'll probably learn quite a bit yourself... In particular, you get a guided tour of parts of the codebase you may not know, from someone who's just been there. Finding bugs: · Yes, but not necessarily as important as you might think. If you've got good unit, integration and system test coverage (and if you haven't, what are you waiting for?), the main issues you might spot in a code review will be for non-functional aspects like concurrency issues, memory leaks etc. Code and design quality: · Very important. Reviews give you a chance to suggest better ways of doing it, whatever it is, and to discuss potential issues with the way the code has been written. Code standardization: · One of the tenets of agile methods is that all code should look the same - it shouldn't be possible to tell from the code who wrote it. That way you can concentrate on understanding the code, rather than grappling with trying to parse the code. While you can (and should) use static checkers like Checkstyle to ensure that your basic coding standards have been met, reviews will catch the issues that need human eyes to find. Regulatory issues: · At TNS Payments we operate under pretty tight security requirements, and we have to provide proof of appropriate peer code review to 2 separate external auditors. JCR provides everything we need for this. Requirements: · Python 2.4 or later (2.5 recommended) · For production use, either Postgres 8.x or Mysql 5.x (also works with Sqlite, but this may not be suitable for heavy use) What's New in This Release: Project Review: · Added number of comments for each project on the main page. Note that these only · refresh every minute, so they may not be up to date. · Added explicit wordbreaks between path and filename, to help IE realise it can · wrap the text. This should prevent the page being wider than the browser window in · IE. Still no good solution for Safari... Project Administration: · Added 'suggest' functionality to repository path field when creating new project · (Subversion) · Added information icon to Files tab page if no files already selected · Removed option to select HEAD as original revision (Subversion) · When HEAD is selected as modified revision, this is replaced (on submit) by the latest · revision number in the repository (Subversion) · Added hints for revision values on File Sets page (Subversion) · If diff generation fails for any reason, the project should now be returned to the · 'Initial Setup' state. You'll still need to check the log to find out why the diff · failed · BUG: Validation of revision did not ensure that revision was valid for the project · path (Subversion) Maintenance: · Added summary statistics for projects as on main page System Administration: · Removed logging to console when generating default config file.

JCR Related Software