Hi Paul, looks good - and is nicely commented ;-)
I still think that providing a "blessed" documentation plugin would be another gradle killer-feature. Gradle could leverage some knowledge like: * building a release needs packaging the docs * which changes require doc regeneration * how to link references to the javadoc, groovydoc, etc. * how to link into the *sources*, e.g. for inlining samples in the docs (and all that is in addition to making a standard website à la maven) I can easily picture some projects going to gradle only because of such a feature. cheers Dierk P.S. one feature that I particularly like about grails-doc is that you can so easily navigate from the concepts to the details and vice versa. That's key in understanding anything. Am 23.10.2010 um 22:40 schrieb Paul Speed: > http://filament.svn.sourceforge.net/viewvc/filament/trunk/site/build.gradle?revision=380&view=markup
