Grails has had a stats script for quite a while (thanks to awesome Glen Smith), it's job is to display how many lines of code you've written on your app. Not to be left behind, Griffon provides the same script. As useful as the script is there is a catch: you can't compute LOCs of additional artifacts that are not defined in the source paths found in the stats script.

Well, you couldn't until recently. Starting with Grails 1.2M4 and Griffon 0.2 you'll be able to plug into the stats script and provide additional paths to be counted. Hows does this work you ask? let me introduce you to build events, as explained at the official Grails guide (Griffon events work exactly the same, cool huh?). The stats plugin will publish a StatsStart event, passing a list of maps as parameter. Each entry on that list defines a path to be searched, files found on that path will be counted if they match a certain criteria, mainly their filetype (actually a file suffix). To give you an example these are the default paths of the Grails stats script
def pathToInfo = [ [name: "Controllers", path: "controllers", filetype: [".groovy"]], [name: "Domain Classes", path: "domain", filetype: [".groovy"]], [name: "Jobs", path: "job", filetype: [".groovy"]], [name: "Services", path: "services", filetype: [".groovy"]], [name: "Tag Libraries", path: "taglib", filetype: [".groovy"]], [name: "Groovy Helpers", path: "src.groovy", filetype: [".groovy"]], [name: "Java Helpers", path: "src.java", filetype: [".java"]], [name: "Unit Tests", path: "test.unit", filetype: [".groovy"]], [name: "Integration Tests", path: "test.integration", filetype: [".groovy"]], [name: "Scripts", path: "scripts", filetype: [".groovy"]], ]You'll notice that filetype is a list (it used to be a single String). This is useful when joint-compilation is taken into account, a fact that the Griffon stats plugin relies on, as the path src/main main contains both Groovy and Java sources
def pathToInfo = [ [name: "Models", path: "models", filetype: [".groovy"]], [name: "Views", path: "views", filetype: [".groovy"]], [name: "Controllers", path: "controllers", filetype: [".groovy"]], [name: "Lifecycle", path: "lifecycle", filetype: [".groovy"]], [name: "Groovy/Java Sources", path: "src.main", filetype: [".groovy",".java"]], [name: "Unit Tests", path: "test.unit", filetype: [".groovy"]], [name: "Integration Tests", path: "test.integration", filetype: [".groovy"]], [name: "Scripts", path: "scripts", filetype: [".groovy"]], ]Alright, so how do you plug into this feature? all you to do is add an event handler in scripts/_Events.groovy, like this one (used by Griffon's Scala plugin)
eventStatsStart = { pathToInfo -> if(!pathToInfo.find{ it.path == "src.commons"} ) { pathToInfo << [name: "Common Sources", path: "src.commons", filetype: [".groovy",".java"]] } if(!pathToInfo.find{ it.path == "src.scala"} ) { pathToInfo << [name: "Scala Sources", path: "src.scala", filetype: [".scala"]] } }There is an additional feature, you may redefine how comments and empty lines are matched for a particular path. Provide a value for a locmatcher property. This is how the Griffon Clojure plugin does it:
eventStatsStart = { pathToInfo -> if(!pathToInfo.find{ it.path == "src.commons"} ) { pathToInfo << [name: "Common Sources", path: "src.commons", filetype: [".groovy",".java"]] } // TODO -- match multiline comments -> (comment ...) if(!pathToInfo.find{ it.path == "src.clojure"} ) { def EMPTY = /^\s*$/ pathToInfo << [name: "Clojure Sources", path: "src.clojure", filetype: [".clj"], locmatcher: {file -> def loc = 0 file.eachLine { line -> if(line ==~ EMPTY || line ==~ /^\s*\;.*/) return loc++ } loc }] } }Finally, the default LOC matcher should give better results when a multiline (/* */) comment is found on the source code.

Keep on Groovying!