-
Notifications
You must be signed in to change notification settings - Fork 31
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
Metrics -extension: Most columns are NULL in database table metrics #91
Comments
To execute Metrics extension, you have to install first sloccount, cccc and python-metrics packages. All of them are in Debian. |
Maybe this should be documented in a good way.
For details have a look at https://github.com/MetricsGrimoire/CVSAnalY/blob/master/pycvsanaly2/extensions/Metrics.py and search for "find_program". |
Looks like the Mccabe metrics for Java is not implemented. So if you are analyzing Java source files, those columns will be empty |
I added a small chapter about this tools into the readme: a6b09b9 @linzhp: You are right. Metrics for many languages are not implemented. Maybe this kind of implementation needs refactoring as well. But feel free to add new languages :) @mniemela: Does this help? |
I am implementing mccabe for Java. Checkout https://github.com/linzhp/CVSAnalY/tree/mccabe_for_java. Will create a pull request once it's done. |
Btw, where can you find kdsi and halstead for debian? A quick googling session didn't find those packets. |
@mniemela Try with the |
@linzhp Thanks! Sounds great! |
Also, maybe Metrics should print some error if the additional packages haven't been installed? |
Good idea. Can you create a PR for this? Am Dienstag, 2. September 2014 schrieb Mikael :
|
Hmm, it looks like there are printouts for situations when programs are not installed. However, for some reason I didn't get them when running Metrics. |
@sduenas does CMetrics provide kdsi, halstead and mccabe executables? |
After executing CVSAnalY with Metrics, most of the columns in database table metrics are null. Is this a matter of stuff not being implemented, or is there a bug?
The text was updated successfully, but these errors were encountered: