[ http://issues.apache.org/jira/browse/BEEHIVE-836?page=all ]
Steve Hanson resolved BEEHIVE-836:
----------------------------------
Resolution: Fixed
This is now fixed...with rev.
http://svn.apache.org/viewcvs?rev=202286&view=rev
The fix will appear on the live site in the next hour or two.
> tag library documentation, once a link to the tag class is followed the links
> in the tag class pages are broken
> ---------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-836
> URL: http://issues.apache.org/jira/browse/BEEHIVE-836
> Project: Beehive
> Type: Bug
> Components: Documentation
> Reporter: Krista Baker
> Assignee: Steve Hanson
> Fix For: V1
>
> This affects current documentation that is built from the trunk and the live
> documentation on incubator.apache.org/beehive
> Repro steps:
> Go to the page flow tag library documentation
> (http://incubator.apache.org/beehive/apidocs/taglib/index.html)
> Follow a link to one of the tags
> At the bottom of the tag page, there is a table named Tag Information. From
> this area, click on the Tag Class link.
> The link opens in a new page, this is the page that contains broken links:
> Description of error: The images do not appear, but instead their alternate
> text and the links, even internal page links are broken.
> Reason: There is an extra "org/" in all generated links from these pages. I
> am not sure what the fix is, but the cause appears to be that the generated
> relative links are:
> <A HREF="../../../../../../overview-summary.html">
> when they need to be
> <A HREF="../../../../../../../overview-summary.html">
> (note the 6 ../'s in the first to the 7 in the second)
> I was only able to reproduce this from going through the netui tag
> documentation. The regular javadocs appear to be working correctly.
> Workaround: When the Page Not Found error appears, remove the extra org/
> occurence in the generated URL.. Or find the tag class by navigating within
> the Page Flow java doc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
