jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven Doxia
  • DOXIA-29

APT - local anchor doesn't work

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 1.0-alpha-5
  • Fix Version/s: 1.0-alpha-9
  • Component/s: None
  • Labels:
    None
  • Environment:
    Using maven 2.0 on windows XP

Description

In APT documents, the local anchor definition and references anchor are not correctly processed.
Also, there is no anchor generated automatically for section titles (as mentionned in APT doc)

Sample page : http://doxia.codehaus.org/format.html
--> try to click on the only internal link named "document structure" it has been generated as an external link.

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. DOXIA-47 APT - local named anchors in apt text are not created properly.

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Emmanuel Venisse added a comment - 24/Nov/05 9:35 AM

Fixed.

Show
Emmanuel Venisse added a comment - 24/Nov/05 9:35 AM Fixed.
Hide
Permalink
Vincent Massol added a comment - 09/Sep/06 2:26 PM

Hi Emmanuel,

I'm having the same problem (anchor links not generated properly). I'm using the syntax specified in the Maven APT guide. I've done a "mvn site" on my project . I had removed all doxia artifacts from my local repo to see which ones are used. Both 1.0 alpha 7 and 1.0 alpha 8 are used during the site generation so it seems it wasn't fixed in 1.0 alpha 6 or there's been a regression somewhere. Thus I'm reopening this issue.

It does work if I use the following syntax:

User Guide

 * {{{usage.html#Generating a Clover report when generating the site}Generating a Clover report when generating the site}}

 * {{{usage.html#Generating a Clover report without modifying your POM}Generating a Clover report without modifying your POM}}

 * {{{usage.html#Generating HTML, XML and PDF reports}Generating HTML, XML and PDF reports}}

 * {{{usage.html#Generating historical reports}Generating historical reports}}

 * {{{usage.html#Checking test coverage}Checking test coverage}}

 * {{{usage.html#Using Clover with JDK 1.4 and JDK 1.5 keywords}Using Clover with JDK 1.4 and JDK 1.5 keywords}}

 * {{{usage.html#Specifying a Clover flush policy}Specifying a Clover flush policy}}

 * {{{usage.html#Specifying a custom license file}Specifying a custom license file}}

 * {{{usage.html#Aggregating Clover reports}Aggregating Clover reports}}

 * {{{usage.html#Controlling files to instrument}Controlling files to instrument}}

 []

* {Generating a Clover report when generating the site}

  Blah blah...

But that's not the format specified in the APT guide. The section should also generate an implicit anchor without the need to explicitely create it.

Thanks

Show
Vincent Massol added a comment - 09/Sep/06 2:26 PM Hi Emmanuel, I'm having the same problem (anchor links not generated properly). I'm using the syntax specified in the Maven APT guide. I've done a "mvn site" on my project . I had removed all doxia artifacts from my local repo to see which ones are used. Both 1.0 alpha 7 and 1.0 alpha 8 are used during the site generation so it seems it wasn't fixed in 1.0 alpha 6 or there's been a regression somewhere. Thus I'm reopening this issue. It does work if I use the following syntax:
User Guide

 * {{{usage.html#Generating a Clover report when generating the site}Generating a Clover report when generating the site}}

 * {{{usage.html#Generating a Clover report without modifying your POM}Generating a Clover report without modifying your POM}}

 * {{{usage.html#Generating HTML, XML and PDF reports}Generating HTML, XML and PDF reports}}

 * {{{usage.html#Generating historical reports}Generating historical reports}}

 * {{{usage.html#Checking test coverage}Checking test coverage}}

 * {{{usage.html#Using Clover with JDK 1.4 and JDK 1.5 keywords}Using Clover with JDK 1.4 and JDK 1.5 keywords}}

 * {{{usage.html#Specifying a Clover flush policy}Specifying a Clover flush policy}}

 * {{{usage.html#Specifying a custom license file}Specifying a custom license file}}

 * {{{usage.html#Aggregating Clover reports}Aggregating Clover reports}}

 * {{{usage.html#Controlling files to instrument}Controlling files to instrument}}

 []

* {Generating a Clover report when generating the site}

  Blah blah...
But that's not the format specified in the APT guide. The section should also generate an implicit anchor without the need to explicitely create it. Thanks
Hide
Permalink
Brian Fox added a comment - 02/Jan/07 8:42 PM

I see this too. The section isn't an anchor and anchor generates a link to /site/anchor instead of /site/page#anchor. #anchor does work however.

Show
Brian Fox added a comment - 02/Jan/07 8:42 PM I see this too. The section isn't an anchor and anchor generates a link to /site/anchor instead of /site/page#anchor. #anchor does work however.
Hide
Permalink
Jason van Zyl added a comment - 28/May/07 12:39 PM

Dupe of DOXIA-47 which attempts a patch.

Show
Jason van Zyl added a comment - 28/May/07 12:39 PM Dupe of DOXIA-47 which attempts a patch.

People

  • Assignee:
    Emmanuel Venisse
    Reporter:
    Olivier Berlanger
Vote (3)
Watch (1)

Dates

  • Created:
    08/Nov/05 4:07 AM
    Updated:
    09/Sep/07 1:06 PM
    Resolved:
    28/May/07 12:39 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.