-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot compute churn metrics for SVN XML logs #6
Comments
Yes, you're correct - code churn isn't supported for SVN (only for Git). We could implement support for the text format to get some basic churn metrics for SVN as well. But IIRC I looked into that a few years ago and found out that SVN only supports a single metric; From the log, there's no way to know if a line was added, modified or deleted, right? Thus, the way I've approached code churn in SVN is to traverse the repository, |
I wouldn't like to comment on the challenge of reworking other parts of the tool to support the textual log format. Clojure is still very alien to me at the moment. |
Cool - I wasn't aware of the `diff´ flag. Sounds interesting. It's quite straightforward to support a new format. The parsers are orthogonal to the analysis algorithms; The analyses don't know anything about the different version-control systems. A parser in Code Maat translates the input to a common format that all analyses operate on. So basically we just need to specify a grammar for the SVN text format and hook it in. I'd be interested in giving it a try. However, I probably won't be able to do that in the near future. But I put it in my TODO-queue here. Also, if you have some sample SVN log file with churn data, feel free to send it to me. It would be useful. |
How about data from Apache Subversion itself? It's a pretty complex project with code in C, Java and some Python tests.
svnlog.log contents:
|
I had to limit the size of the log to a day's worth. Any more and GitHub can't deal with it. |
Just curious if you had reviewed the StatSVN (http://wiki.statsvn.org/) or svnstat tool (http://svnstat.sourceforge.net/)? The first one does heat maps and tracks changes by developer/date using the SVN diff and a SVN log file. |
Yes, I tested statsvn just last year. The heat map is nice and the churn graph gives an overview of the general trend. If you work with Subversion, statsvn is a good complement to Code Maat. Your Code as a Crime Scene:
Just curious if you had reviewed the statsvn tool? It does heat maps and tracks changes by developer/date using the SVN diff and a SVN log file.— |
Using the SVN log format mentioned in the README file for code-maat:
I have encountered the following error:
This issue arises from the choice of using SVN's XML log format, which does not support reporting the diffs. The text format supports diffs but may be harder to parse.
The text was updated successfully, but these errors were encountered: