>
> 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
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
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
>
> 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
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).
---
On 31.01.2016 21:29, Thibault Kruse wrote:
Are Antlr 4 and Jva 8 syntax linked somethow, meaning is there a hard
problem describing certain java8 features using whatever antlr version
is used right now?
They are linked in that way, that it does not really make sense to do
bigger syntax chang
So one thing that could be useful already is to add stories either in
JIRA or github for each of these epic (in size) issues individually,
where all discussions can be followed. Then a Roadmap document could
list these "epics" as large things on the horizon, without any
specific order or deadline.
>
> 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!
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
