db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6065) LockTable API link in the documentation is broken
Date Fri, 08 Feb 2013 17:27:13 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase resolved DERBY-6065.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.10.0.0
    Issue & fix info:   (was: Patch Available)

Committed DERBY-6065-code.diff to code trunk at revision 1444154. 

Thanks again, Rick. I can reopen this issue if anyone finds more things to correct.
                
> 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
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.10.0.0
>
>         Attachments: DERBY-6065-2.diff, DERBY-6065-2.diff, DERBY-6065-2.stat, DERBY-6065-2.stat,
DERBY-6065-2.zip, DERBY-6065-2.zip, DERBY-6065-code.diff, DERBY-6065.diff, DERBY-6065.stat,
DERBY-6065.zip, StatementCache.html
>
>
> 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

Mime
View raw message