AgileReview provides you with an easy possibility to do code reviews in your favorite IDE. Code reviews are a powerful meaning for quality assurance, but switching between spreadsheets and code is very time consuming. With AgileReview you can comment and discuss code without leaving the IDE and more important: without leaving the code. Features of AgileReview:
- Refactoring stability (within file): Comments stay at the code snipped which you intended to comment, even if the file is edited
- Refactoring stability (outside file): Comments stay connected to the right file, even after moving or renaming viathe eclipse refactoring mechanism
- Fight complexity: Close reviews to hide their comments or simply filter your comments by keywords
- Generic language support: Built-in support for Java, XML and PHP, but it is easy to define your own language support via the preferences
- Team support: Share your comments with other developers, using your favorite version management client - quite without conflicts.
- Export metrics: Export data about your reviews to an Excel template, to do advanced analysis
- Bug/Feature support: Four motivated developers, always eager to fix the bugs you find or consider your feature requests, see bug/feature tracker
For more information see quickstart or visit our homepage
Categories: Code Management, Team Development, Tools
Tags: PHP, code review, java, xml, commit comments, version control, team, review, peer review, reviews, comment
Additional Details
Eclipse Versions: 2022-12 (4.26), 2022-09 (4.25), 2022-06 (4.24), 2022-03 (4.23), 2021-12 (4.22), 2021-09 (4.21), 2021-06 (4.20), 2021-03 (4.19), 2020-12 (4.18), 2020-09 (4.17), 2020-06 (4.16), 2020-03 (4.15), 2019-12 (4.14), 2019-09 (4.13), 2019-06 (4.12), 2019-03 (4.11), 2018-12 (4.10), 2018-09 (4.9), Photon (4.8), Oxygen (4.7), Neon (4.6), Mars (4.5), Luna (4.4), Kepler (4.3), Juno (4.2, 3.8), Previous to Juno (<=4.1)
Platform Support: Windows, Mac, Linux/GTK
Organization Name: AgileReview Team
Development Status: Beta
Date Created: Sunday, February 6, 2011 - 09:17
License: Apache 2.0
Date Updated: Thursday, January 19, 2023 - 09:01
Submitted by: Malte Brunnlieb
| Date | Ranking | Installs | Clickthroughs |
|---|---|---|---|
| October 2024 | 0/0 | 0 | 1 |
| September 2024 | 435/642 | 11 | 12 |
| August 2024 | 559/641 | 3 | 14 |
| July 2024 | 477/663 | 8 | 18 |
| June 2024 | 556/681 | 4 | 30 |
| May 2024 | 408/682 | 16 | 23 |
| April 2024 | 501/687 | 8 | 15 |
| March 2024 | 459/694 | 12 | 14 |
| February 2024 | 461/687 | 10 | 277 |
| January 2024 | 497/691 | 7 | 21 |
| December 2023 | 623/671 | 2 | 13 |
| November 2023 | 431/686 | 15 | 9 |
Marketplace Drag to Install Button
By adding the following code below to your website you will be able to add an install button for AgileReview.
HTML Code:
Markdown Syntax:
Output:
Reviews Add new review
Really nice plugin!
Submitted by Thomas Arnbjerg on Wed, 09/25/2019 - 08:52
Provides the ability to post review comments in your favorite environment with all the tools available in Eclipse. Beats the online tools by lengths.
Can also be used to annotate the code with comments without poluting the source code.
Never change the source code with your review annotations!
Submitted by Pavan G on Fri, 09/21/2018 - 06:15
Alpesh Shah above expressed a very sensible feedback and team failed to recognize it. sad. Guys! your tool is wonderful however, you should never fiddle around with source code, instaed have more info in your review.xml file. something like, file name and line number. Its okay, even things dont match when someone update the source and line numbers change. Perhaps you can offer a configuration setting in which user can choose (i) inline code annotations or (ii) no change in source, all info will be in your xml file with warning message that, it might not sync if someone update the code file and line numbers change.
Looking forward to your comments/reply.
Re: Never change the source code with your review annotations!
Submitted by Peter Reuter on Thu, 09/27/2018 - 04:05
In reply to Never change the source code with your review annotations! by Pavan G
Hi Pavan G, see my reply to Alpesh Shah's comment :)
Re: Never change the source code with your review annotations!
Submitted by Malte Brunnlieb on Fri, 02/08/2019 - 03:55
In reply to Never change the source code with your review annotations! by Pavan G
Hi, an opt-out might be a solution for that.
The main focus of that tools was the stability of review comments against refactorings, which could just be assured by adding marks to the code. I really know your fears about letting any tool change your code. Basically, this design decision has been made in the very beginning as of large software projects needs to get refactoring stable code comments.
Anyhow, I will take your feedback into account. Please don't hesitate to add your feature request in the GitHub issue tracker. Thanks.
Re: Never change the source code with your review annotations!
Submitted by Jake .. on Sat, 01/16/2021 - 01:41
In reply to Never change the source code with your review annotations! by Pavan G
Can't you connect the source file in such a way that changes to it changes the xml file and keeps it in sync?
Very useful tool - marker would be appreaciated
Submitted by Alpesh Shah on Mon, 11/28/2016 - 01:48
I found this tool fulfill almost all requirement for code review within eclipse. Only one point I would like to improve is, for every review comment, an inline comment is added in code which need to be committed along with code. This sometimes clutter the code and it also means that you need to checkout & checkin code even when you don't make any changes to code but just invalidate review comment. Instead of inline comment, if there is just marker on left bar (like how eclipse shows problem or sonar shows violations) could be perfect solution.
Re: Very useful tool - marker would be appreaciated
Submitted by Pavan G on Fri, 09/21/2018 - 06:16
In reply to Very useful tool - marker would be appreaciated by Alpesh Shah
Well said!
Re: Very useful tool - marker would be appreaciated
Submitted by Peter Reuter on Thu, 09/27/2018 - 04:04
In reply to Very useful tool - marker would be appreaciated by Alpesh Shah
Thanks for your feedback! Linking code and comments, even if the code got refactored, is one of the core features of AgileReview. The easiest way to ensure this is by adding markers in the code. AgileReview was constructed around this principle. Showing markers like problems or sonarlint violations is not working with comments as these markers of other tools result from static code analysis which can be performed on demand. Have you tried tools like Gerrit, which are based on individual commits? Maybe these suit your needs more.
Btw: AgileReview is open source. Feel free to contribute your suggestions as pull requests via GitHub :)