[
http://jira.codehaus.org/browse/JXR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164263#action_164263
]
Matthew Beermann commented on JXR-10:
-------------------------------------
This issue hasn't had any updates in a long time; any progress? We have a
regulatory requirement to link each of our functional requirements to one or
more test cases, and as the reporter said, line numbers tend to be very
brittle...
> Create a named anchor for each symbol like Javadoc does
> -------------------------------------------------------
>
> Key: JXR-10
> URL: http://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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
