[
https://issues.apache.org/jira/browse/GROOVY-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104255#comment-17104255
]
Mikko Värri commented on GROOVY-9547:
-------------------------------------
For Java source files, all the tags seem to be resolved when the template asks
for the comments. For Groovy, the comments are formatted right after reading
the source file. So this issue, I think, only affects Groovy code.
Created a PR that postpones the tag hanling for groovy source, too.
> @see tags are not working properly
> ----------------------------------
>
> Key: GROOVY-9547
> URL: https://issues.apache.org/jira/browse/GROOVY-9547
> Project: Groovy
> Issue Type: Bug
> Components: GroovyDoc
> Affects Versions: 3.0.3
> Reporter: Damir Murat
> Priority: Minor
> Attachments: image-2020-05-11-00-25-12-464.png,
> image-2020-05-11-00-25-58-871.png, image-2020-05-11-00-27-49-744.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With Groovy 3.0.3, Groovydoc does not render @see tags properly. When trying
> to link on another class in the same package from the class description, the
> linked class name is rendered, but the link is not created:
> !image-2020-05-11-00-25-58-871.png!
> Another case is when @see is used from a method description trying to link a
> method in another class in the same package. In this scenario, method name is
> duplicated, and the link is missing. Something like this:
> !image-2020-05-11-00-27-49-744.png!
> There might be other scenarios. These two are just those that I stumbled upon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
