|
From: Doug C. <do...@cu...> - 2006-11-29 18:11:17
|
I think StatCVS, StatSVN and Maven are cool so I started a StatSCM (Source Code Management) Maven 2 plug-in. The design brief was a Maven 2 plug-in that generates StatSVN reports as part of a Maven 2 Site build. This now works but is yet to get to the release stage. However it works for me and my boss and so stage one is complete. It is starting to get an audience and so should mature to a release stage soon. For stage 2 of the project I wanted to make the Plug-in work for CVS and SVN because this should be easy to do. I have now found that you have done a Maven 2 plug-in for CVS. Your plug-in is more mature than mine and better integrated into the Maven Reporting API. Therefore it would make sense to merge projects? I would suggest the following: SCM independant (OK works for SVN and CVS). Wraps around StatSVN and StatCVS and has them as dependancies. Common Config parameters. Very minimal effort to integrate into an Maven 2 project. Stage 3: Design to allow implementation of other SCM systems. Try to use the maven-scm interface to remove dependancy on the command line. If we succeed then it could bring the StatXXX reports to the Maven 2 users in a very easy to implement way. This would increase the audience of these tools. I have set up the project http://stat-scm.sourceforge.net/ and we can use this as a platform, start a new platform or use one of the existing platforms. There are 3 projects in the StatXXX and I do not really want to start a new one but I think that this is a worth while exercise with a clear brief. Are you interested? Doug Culnane |