groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andres Almiray <>
Subject Re: API document generation
Date Mon, 25 Jan 2016 08:49:15 GMT
AFAIK you can't use Javadoc doclets without relaying on the Javadoc API,
this is why you can't use Asciidoclet with Groovydoc (believe, I tried
several options).
Wrapping a doclet and adapting it for Groovydoc is not an option either
(tried that too).

The only option for standard doclets to work with Groovydoc is for
Groovydoc to be base don the standard Javadoc API.

Java Champion; Groovy Enthusiast
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.

On Mon, Jan 25, 2016 at 9:37 AM, Peter Ledbrook <>

> 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:

View raw message