[The Java Posse] Tracking code changes by devs

2010-01-30 Thread Rakesh
Hi all, I've been tasked with monitoring all the dev check ins so I can do a code review. We've had alot of issues around code quality. Essentially, I need to be able to know what java classes were involved in a piece of functionality and then go through it with the dev. Is there a way to do

Re: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Graham Allan
I've not used it, but I've heard good things about Atlassian's FishEye... Kind regards, Graham Hi all, I've been tasked with monitoring all the dev check ins so I can do a code review. We've had alot of issues around code quality. Essentially, I need to be able to know what java classes were

Re: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Jan Goyvaerts
Eclipse does that quite well. Ask for the changes and enable the change sets. This will show the subversion commits in a chronological order together with the files of the commit. If my memory serves me well you right click on a file and ask for the annotations. each line of code is preceded by

Re: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Tony Childs
We use the Maven Findbugs plugin in combination with the Hudson Findbugs plugin, but that might not be comprehensive enough for your needs. You might also look at Sonar http://sonar.codehaus.org/. I haven't used it, but I hear good things. On Sat, Jan 30, 2010 at 9:43 AM, Rakesh

Re: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Kevin Wright
I'm 100% behind that one, you can be working with sonar out of the box in seconds, and it really does give you some fantastic metrics. It doesn't have the best documentation in the world, but it's mostly intuitive so you really don't miss it. On 30 January 2010 17:45, Tony Childs

Re: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Marcelo Fukushima
we use a combination of peer review (no code gets commited without a revisor: user ) and tag each commit with its associated JIRA issue (just puttin the issue name in the commit comment). That way, with the JIRA plugin, we can see for each funcionality associated commits, etc etc on a (unrelated)

[The Java Posse] Re: Tracking code changes by devs

2010-01-30 Thread Stephen Gregory
OH. Also I've found Track very handy. Even if you don't use the built-in ticket tracker, it is great for searching through commit messages and code. So if they refer to the ticket/issue#/whatever you use in their commit message you can easily find all of the related commits. And we use the

RE: [The Java Posse] Tracking code changes by devs

2010-01-30 Thread Todd Costella
We use Crucible from Atlassian. It rocks. It supports both precommit reviews (via patches) or post commit reviews against all the major source control systems out there (we use subversion). Highly, highly recommend it. Todd -Original Message- From: javaposse@googlegroups.com on