[
http://jira.codehaus.org/browse/DOXIA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257601#action_257601
]
Lukas Theussl commented on DOXIA-397:
-------------------------------------
I have added a [test case|http://svn.apache.org/viewvc?rev=1074151&view=rev]
that gets broken by the attached patch. I think this is a rather common use
case, as mentioned above, fixing this will break a lot of stuff (note that apt
does not distinguish anchor names from anchor text, ie something like <a
name="name">text</a> is not possible in apt, so there are many examples of
anchors like {anchor with spaces}).
I agree it's annoying, but I'd prefer to postpone a fix for this until a major
version change. Until then I suggest to use abolute links for javadocs.
> Cannot link to javadoc methods
> ------------------------------
>
> Key: DOXIA-397
> URL: http://jira.codehaus.org/browse/DOXIA-397
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Apt, Module - Xdoc
> Affects Versions: 1.1.3
> Reporter: Lukas Theussl
> Attachments: apt-link-fix.diff
>
>
> Using a link to a javadoc method like
> {noformat}
> {{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
> {noformat}
> the apt parser removes the brackets of the anchor. The same thing happens
> with xdocs and probably other formats. Note that non-ascii characters are not
> legal in anchor names, but they should be replaced by their hex values, see
> http://www.w3.org/TR/html401/appendix/notes.html#non-ascii-chars.
--
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
