5
2007
Calculating stats for your Grails project
After developing in Grails for a while, I went to a Rails talk by Matt. He demoed developing a little blogging app, and I recognised that I could do most of what he was talking about just as quickly and easily in Grails.
But one cool little thing he demoed was the “rake stats” command. This gave you a bunch of metrics on your project (lines of code, test/code ratios, NCLOC, etc). Check out a sample run.
Anyways, I thought it was a neat feature, and I was keen to run a similar thing for groovyblogs, so I set aside a lunch hour putting together a cheap and cheerful version in Groovy. Certainly not anywhere near as feature complete, but it’ll get us started, and maybe someone out there will pick up the batton and run with it. Here’s my output from a “grails stats” command when run on the groovyblogs source base:
+----------------------+-------+-------+
| Name | Files | LOC |
+----------------------+-------+-------+
| Controllers | 7 | 588 |
| Domain Classes | 3 | 101 |
| Jobs | 3 | 66 |
| Services | 6 | 618 |
| Tag Libraries | 2 | 207 |
| Tests | 11 | 66 |
| Groovy Helpers | 5 | 179 |
+----------------------+-------+-------+
| Totals | 37 | 1825 |
+----------------------+-------+-------+
Mine is very rudimentary, simply calculating the number of files and total lines of code (sorry, no smart stuff around whitespace or comments).
The amazing part is how quick is it to whip this sort of thing up in groovy. Building that table I became acquainted with the String.padRight() and String.padLeft() enhancements. Add the File.eachFileRecurse closure and a sprinkling of Expandos, and voila! You’ve saved an incredible amount of mucking about!
Converting to a command that can integrate with Grails commandline was pretty much a drag and drop to the “scripts” directory along with a few scaffold lines to return the name of the target. A snack!
Anyways, I’ll talk to the Grails boys and see if I can get it added to a future release. In the meantime, if you’re keen to use it in your own project, grab Stats.groovy from the downloads directory, and put it in your $GRAILS_HOME/scripts directory. Then you’re only a “grails stats” away from getting a lay of the land.
4 Comments + Add Comment
Leave a comment
Glen Smith
Archives
- April 2012
- March 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003

An article by Glen





Really nice Glen. You keep suprising!
I would say add JIRA issue and attach the patch.
Cheers,
Marcel
Good idea, Marcel. Will do it today.
In other news, I decided to filter whitespace in source files for stats calculations (since it’s a one-liner). Have updated the download.
My linecount has now dropped to 1425.
Glen – out of interest why use Expandos and not nested maps?
Marc, no good reason. I just have a soft spot for Expandos. That whole “assigning a closure to a property” thing just makes me love ‘em. But for this script, the map does probably make more sense. Nice pickup.