[ 
https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569958#comment-13569958
 ] 

Dag H. Wanvik commented on DERBY-6065:
--------------------------------------

Looks like these links presume a "dev" location for the latest docs, cf this 
link: 

http://db.apache.org/derby/docs/dev/devguide/cdevconcepts30291.html

Right under the "docs" directory there are currently only version directories:
 
10.1, 10.2, ..., 10.9. There is no "dev" directory with the latest trunk docs 
anymore,
these are now at:

https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/{devguide,
 ... }

Rather than having to hand edit all the wiki documents referencing the "dev" 
location, maybe we could
make "dev" a symlink" the latest released docs, i.e. "10.9"? [Plus a step to 
update the link in the instructions for publishing a new release docs.. ]

Or is it important/crucial that the wiki always references the trunk docs?

                
> LockTable API link in the documentation is broken
> -------------------------------------------------
>
>                 Key: DERBY-6065
>                 URL: https://issues.apache.org/jira/browse/DERBY-6065
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.9.1.0
>            Reporter: Bryan Pendleton
>            Priority: Minor
>
> I happened to notice that some of the links in the documentation are broken.
> For example, on 
> http://db.apache.org/derby/docs/10.9/devguide/cdevconcepts50894.html
> the link to LockTable API documentation is broken.
> There are also broken links to the documentation in the wiki, but that's not 
> something we track with JIRA issues, I think. But it would be nice to figure 
> out if we can clean up those links easily. For example, on  
> http://wiki.apache.org/db-derby/LockDebugging there are broken links to the 
> LockTable API documentation, as well as to the SYSCS_DIAG table documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to