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 the revision number of the last change at that line. You can ask to show the user too. On Sat, Jan 30, 2010 at 16:43, Rakesh <rakesh.mailgro...@gmail.com> wrote: > 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 this? I guess either need to track changes by a > particular dev (over a certain time period) or ask the devs to put some > marker in the check in comment (probably the story number)? > > We use subversion. So I guess some magic command line tinkering? What about > the code review tools out there? > > Cheers > > Rakesh > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to javapo...@googlegroups.com. > To unsubscribe from this group, send email to > javaposse+unsubscr...@googlegroups.com<javaposse%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
