Re: API document generation

2016-02-01 Thread Jochen Theodorou
On 01.02.2016 16:13, Sean Gilligan wrote: I'm also wondering whether others think groovydoc is just fine as it is, It's not fine. In my opinion it's one of the biggest frustrations with Groovy. Especially the fact that you can't use it for both Java (7+) and Groovy. And Asciidoclet suppo

Re: API document generation

2016-02-01 Thread Sean Gilligan
> > I'm also wondering whether others think groovydoc is just fine as it is, It's not fine. In my opinion it's one of the biggest frustrations with Groovy. Especially the fact that you can't use it for both Java (7+) and Groovy. And Asciidoclet support would be awesome!

Re: API document generation

2016-02-01 Thread Andres Almiray
Well, Groovydoc is a parallel API inspired by Javadoc, so retrofitting would entail grabbing the real Javadoc tooling API and adding extension points that can handle Groovy syntax such as understanding properties, closures and other stuff (such as default values in method parameters IIRC). ---

Re: API document generation

2016-02-01 Thread Peter Ledbrook
> > I'm afraid not. Javadoc is a very specific tool that looks exclusively > into Java sources. > My experience in the past extending Groovydoc tells me the only way to > integrate with Javadoc tooling and doclets is to embrace and extend the > Javadoc API. > How feasible is it to retrofit Groovyd

Re: API document generation

2016-02-01 Thread Andres Almiray
I'm afraid not. Javadoc is a very specific tool that looks exclusively into Java sources. My experience in the past extending Groovydoc tells me the only way to integrate with Javadoc tooling and doclets is to embrace and extend the Javadoc API. --- Java Cha

Re: API document generation

2016-02-01 Thread Guillaume Laforge
Is it possible to make JavaDoc look into non-Java sources? Also what about things which are not part of the JavaDoc model, like "properties"? On Mon, Feb 1, 2016 at 9:18 AM, Peter Ledbrook wrote: > The only option for standard doclets to work with Groovydoc is for >> Groovydoc to be base don the

Re: API document generation

2016-02-01 Thread Peter Ledbrook
> > The only option for standard doclets to work with Groovydoc is for > Groovydoc to be base don the standard Javadoc API. > Is that something that's worth aiming for? Is it even feasible? I'm also wondering whether others think groovydoc is just fine as it is, since this thread has so little at

Re: API document generation

2016-01-25 Thread Andres Almiray
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 w