{iframe:src=http://update.sonarsource.org/plugins/scmstats.html|width=700|height=250|frameborder=0}
Your browser does not support iframes.
{iframe}

Upgrade from 0.1 to 0.2

If you upgrade from 0,1 to 0.2 you'll need to run a new analysis to see the widgets of authors activity and commits per author.

Description / Features

The plugin computes and feds feeds Sonar with four (54) new metrics : Authors Activity, Commits / Author, Commits / Clock Hour, Commits / Week Day and Commits / Month.
Four Five(5) project widgets ( under the SCM category ) display these metrics using graphical representations.

...

The "Author activity" widget (available since version 0.2) displays a stacked 3D bar chart about top 10 authors activities types : New files(green), modifications(blue) , deletions(red)

...

1. Install the SCM Stats plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
2. If you plan to use this plugin with non-maven projects, or SCM access is avalable available only with username/password or no SCM information is included in project's pom.xml you have to also install the SCM Activity plugin 
3. Restart the Sonar server

4. Set the SCM URL of your project (see SCM URL Format) by setting the sonar.scm.url property of SCM Activity plugin. For Maven projects this is automatically discovered if it's already set in pom.xml

5. Set the SCM user / password (if needed) by setting the sonarc.scm.user.secured and sonar.scm.password.secured properties of SCM Activity plugin

6. Launch a new quality analysis and the metrics will be fed

   Warning
   title Important notice
   The sonar.scm.user.secured and sonar.scm.password.secured properties end with secured which means that we need to authenticate the analyzer to use them. So you have two possible solutions. A: If you've set these properties at project or global settings then use/set the sonar.login and sonar.password properties in your analyzer to authenticate it. B: You can set sonar.scm.user.secured and sonar.scm.password.secured properties directly in your analyzer wihtout specifying the  sonar.login and sonar.password properties. For example if you use maven then in case A (scm properties set in project/global settings) the maven cmd could be like this  No Format nopanel true mvn sonar:sonar -Dsonar.login=admin -Dsonar.password=admin   and in case B (scm properties set directly to analyzer) like this  No Format nopanel true mvn sonar:sonar -Dsonar.scm.user.secured=<SCM_USER> -Dsonar.scm.passoword.secured=<SCM_PWD>

Grabbing stats for multiple periods

...

Plugin version	0.1	0.2
Source Control
Subversion
Git
Mercurial
CVS

Metrics Definitions

Future Work (Open Issues)

Plenty !!! Waiting for your ideas as well!

Change Log

...