[
https://jira.codehaus.org/browse/JXR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359436#comment-359436
]
Michael Osipov edited comment on JXR-10 at 12/20/14 4:38 PM:
-------------------------------------------------------------
This cannot be solved with JXR unless completely rewritten. JXR is completely
line-based. It would require JXR to create an AST from the source file to be
aware of the current node. This would be a reimplementation of Javadoc in some
way.
was (Author: michael-o):
This cannot be solved with JXR unless completely rewritten. JXR is completely
line-based. It would require JXR to have to create an AST from the source file
to be aware of the current node. This would be a reimplementation of Javadoc in
some way.
> Create a named anchor for each symbol like Javadoc does
> -------------------------------------------------------
>
> Key: JXR-10
> URL: https://jira.codehaus.org/browse/JXR-10
> Project: Maven JXR
> Issue Type: Improvement
> Components: jxr
> Reporter: Laurent Caillette
> Priority: Minor
>
> I want to reference source code from XDoc. By now I'm writing a link like
> this:
> <a href="./../xref/com/acme/foo/Foo.html#127">method here</a>
> The problem is, my link can lead to a wrong place just after a few cosmetic
> changes in source code. Of course, automatic link check will not guess the
> link went wrong.
> It would be nice to generate named anchors in XRef the same way Javadoc does,
> supporting a link like this from XDoc:
> <a href="./../xref/com/acme/foo/Foo.html#bar(Object)">method here</a>
> Another way to achieve the same result would be to parse Java comments to
> find a special expression to be transformed in a named anchor, but the
> Javadoc way seems more straightforward.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
