Name |
Sonar SCM Activity Plugin |
Authors |
|
Jira |
TBA |
Latest version |
0.1-SNAPSHOT |
License |
Apache 2 |
Sources |
TBA |
Download |
TBA |
Ideas
See http://n2.nabble.com/New-Developer-Activity-Plugin-tp4240105p4240105.html
OLD - Evgeny Mandrikov
Looks like start point can be a maven-changelog-plugin or scmchangelog-maven-plugin.
I'm looking for simplest way of how to support all SCMs (see http://maven.apache.org/scm/scms-overview.html). SCMs in importance order:
- SVN
- Git
Metrics:
- Last commit
- Number of commits since last release (see http://n4.nabble.com/Unreleased-plugin-changes-tp990541p990541.html)
Chad Retz
I was going to attempt to do this as well. IMO, you should split the information into two types: ETL processed and live. Reason is, you can get so much information parsing the logs. Actually, you can just take the code from StatSVN and StatCVS, and translate something like GitStats to Java for the ETL portion. This should make your life much easier developing this, and give a lot more cool features.
Compatibility matrix
Plugin |
0.1-SNAPSHOT |
---|---|
Sonar |
1.12+ |
Description / Features
TBA
Usage & Installation
TBA
Known limitations
TBA
Troubleshooting
TBA
Changelog
TBA