Gilles Querret

Won't fix, use JsonDocumentation task. I confirm that the generics information is available there, as well as the input/output mode.

ClassDocumentation won't be maintained anymore (at least not by Riverside). Multiple reasons for that: * it depends on ast.jar which is much more difficult to maintain than proparse * entirely...

> Is there a usable example which shows how the JsonDoc should be used and how to consume the results? Documentation: https://wiki.rssw.eu/pct/JsonDocumentation.md No example on how to consume the result....

> `` Mistake is probably here ; you have to point to the source directory (in order to execute the parser)

@DustinGrau-PSC Comments are not available from the rcode, so source code is needed. RCode contains the exact structure (even method signatures with .net types), so all methods / properties /...

> I've been able to get a successful run from JsonDocumentation and it appears to produce all the basic information I would expect in the JSON output, though it doesn't...

Won't be fixed in AblDuck (unless @spazzymoto takes care of it), and issue is not present in JsonDocumentation.

Won't be fixed in PCT.

Will only be handled in JsonDocumentation task. See [documentation](https://github.com/Riverside-Software/pct/wiki/StandardCommentBlock#deprecated-annotation)

My work on this topic is a bit far away, but I didn't find any way on how to solve this issue. Unless additional info can be provided, this issue...