Add this URL to your Eclipse Installation to reach this solution's update site.
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:
For more information see quickstart or visit our homepage
Unsuccessful Installs in the last 7 Days: 0
By adding the following code below to your website you will be able to add an install button for AgileReview.HTML Code:
Submitted by Pavan G on Fri, 2018-09-21 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.
Submitted by Peter Reuter on Thu, 2018-09-27 04:05
Hi Pavan G, see my reply to Alpesh Shah's comment :)
Submitted by Alpesh Shah on Mon, 2016-11-28 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.
Submitted by Peter Reuter on Thu, 2018-09-27 04:04
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 :)
Submitted by Pavan G on Fri, 2018-09-21 06:16
Back to the top