1.0.41

Fixed issues:

• do not use log4j

1.0.40

Fixed issues:

• correct fix for #18 (previous fix did not work for projects with different id and name)

1.0.39

Fixed issues:

• review statistics SQL query does not work with numerical PKs (#18)

1.0.38

New features:

• allow to specify repositories which are not shown in the Code Review extension, are not considered for any review actions, are ignored by FastTrackReviewCondition and do not trigger any checks in Code Review Checker

1.0.37

New features:

• allow to specify extra permitted projects for Code Review Checker in addition to the scope of the job itself
• allow to execute Code Review Assigner job on behalf of different user

1.0.36

New features:

• context of the current compare is always visible even if compared file does not fit to screen
• comment can be added while reviewing
• it is possible to review all revisions and reopen the item with "Review all & reopen" command
• it is possible to auto-assign reviewers with newly added job codereview.assigner
• users can no longer select revisions which would not be reviewed anyway (tooltip gives the reason)
• "Review ..." commands are renamed appropriately if some revisions cannot be reviewed by current user so that it is apparent what is going to happen when invoked

Fixed issues:

• error logging was improved so that it is easier to find out what is wrong
• fastTrackPermittedLocationPattern is no longer required if fast track reviews are not used
• jumping to the file from the list at the top of the compare view will also change the reference position used by Prev and Next buttons
• error is no longer logged when compare view attempts to show changes in a file which was added and removed at the same revision
• link to external revision in the Code Review Checker notification email is no longer wrong
• review action should no longer occasionally lead to blank page
• fixed problem with Reopen not available when some revisions cannot be reviewed by current user

1.0.34

New features:

• form extension is read-only unless user has role defined by configuration property reviewerRole
• past reviewers no longer have to have the reviewer role assigned forever as their names can be defined by configuration property pastReviewers so that they are still known to the checker job
• reviewers cannot review their own changes
• checker job can be configured with job property permittedItemsQuery so that it will report items with linked revisions not matched by that query
• form extension can be switched to special conflicts prevention mode (if configuration property preventReviewConflicts is set to true) when current reviewer either has to be set in the codeReviewer field or [ Start review ] button has to be pressed first
• differences are shown for all text files (marked as such in Subversion)

Fixed issues:

• form extension crashed with invalid data