DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9688>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9688 [SUBMIT] JavaNcssTask Summary: [SUBMIT] JavaNcssTask Product: Ant Version: 1.6Alpha (nightly) Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I've just written a new Ant task that wraps the JavaNCSS library (http://www.kclee.com/clemens/java/javancss/) for determining source code metrics and would like to propose it be added to Ant's optional.jar. The task enables metrics about a project's source code to be collected during a build. Metrics can be collected globally and at class and function level and include the number of non-commenting source statements (NCSS) and function Cyclomatic Complexity Number (McCabe metric). Packages, classes, functions and inner classes are counted and average values calculated. Javadoc coverage can also be determined. I have already spent some time looking at Steve Jernigan's existing Ant task for JavaNCSS on SourceForge (http://sourceforge.net/projects/javancss2ant/) with a view to combining the functionality his task provides (metrics threshold checking) with mine (report generation). Clemens Lee, the author of JavaNCSS, has also been involved in this discussion. In the end we decided this would not be possible as Steve's code requires the JavaNCSS libraries be present at compile time which appears to be in conflict with the principle that all Ant optional tasks should stand alone from external libraries. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
