Hey, I tweeted about including some of MrHaki's Groovy Goodness examples in the API documentation and this led to discussions about the technology behind the generations of those docs.
I'm not that familiar with the limitations of groovydoc, but I have heard complaints about it. For example, it seems you can't use doclets designed for javadoc. Perhaps it's time to discuss an alternative system to groovydoc? Maybe one that's independent of javadoc. So, do people think we need to consider a new API doc system, or does the existing one just need a little love to add things like AsciiDoc support or integrate extension method (Groovy JDK) and normal (Groovy API) docs? Peter -- Peter Ledbrook t: @pledbrook w: http://www.cacoethes.co.uk/
