Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.3
    • Fix Version/s: 1.4
    • Labels:
      None
    • Number of attachments :
      1

      Description

      Using a link to a javadoc method like

      {{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
      

      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.

        Issue Links

          Activity

          Hide
          vincent laugier added a comment -

          I am currently using doxia apt to generate a maven website (with maven-site-plugin:3.0-beta-3)

          The problem is still the same:

          [WARNING] [APT Parser] Modified invalid link: 'initializeGrid(org.primefaces.component.panelgrid.PanelGrid)' to './apidocs/org/objectwiz/web/backingbean/EjbClientBackingBean.html#initializeGridorg.primefaces.component.panelgrid.PanelGrid'

          I guess that there is nothing to be done (the bug would have been fixed by now).

          How can we include html into a apt document ?

          Show
          vincent laugier added a comment - I am currently using doxia apt to generate a maven website (with maven-site-plugin:3.0-beta-3) The problem is still the same: [WARNING] [APT Parser] Modified invalid link: 'initializeGrid(org.primefaces.component.panelgrid.PanelGrid)' to './apidocs/org/objectwiz/web/backingbean/EjbClientBackingBean.html#initializeGridorg.primefaces.component.panelgrid.PanelGrid' I guess that there is nothing to be done (the bug would have been fixed by now). How can we include html into a apt document ?
          Hide
          Michael Osipov added a comment -

          Vicent, unless fix doxia yourself the problem will persist. The problem is that the standard JavaDoc doclet generates invalid anchors and doxia rejects them.

          Show
          Michael Osipov added a comment - Vicent, unless fix doxia yourself the problem will persist. The problem is that the standard JavaDoc doclet generates invalid anchors and doxia rejects them.
          Hide
          vincent laugier added a comment -

          Hello Michael,

          I have eventually decided to use some absolute links

          and filter my apt files for convenience

          http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

          Thanks

          Show
          vincent laugier added a comment - Hello Michael, I have eventually decided to use some absolute links and filter my apt files for convenience http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html Thanks
          Hide
          Michael Osipov added a comment -

          Have you tried to use URI escapes?

          Show
          Michael Osipov added a comment - Have you tried to use URI escapes?
          Hide
          Robert Scholte added a comment -

          Fixed in r1465234
          A link with a single '#' will be translated to a Doxia-ID.
          A link with '##' (which would normally be illegal) will copy the anchor as is. This means that the developer is responsible for the correct URL encoding!

          Show
          Robert Scholte added a comment - Fixed in r1465234 A link with a single '#' will be translated to a Doxia-ID. A link with '##' (which would normally be illegal) will copy the anchor as is. This means that the developer is responsible for the correct URL encoding!

            People

            • Assignee:
              Robert Scholte
              Reporter:
              Lukas Theussl
            • Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: