db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6065) LockTable API link in the documentation is broken
Date Mon, 04 Feb 2013 16:52:28 GMT

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

Rick Hillegas commented on DERBY-6065:
--------------------------------------

Hi Kim,

In general, the engine javadoc is assumed to not be stable. It changes from one release to
another. I don't think that the user guides should refer people to unstable javadoc. The only
javadoc mentioned by the user guides should be javadoc that is in the public api or that is
included wholesale in the user guides themselves. Maybe what we need to do is log a related
JIRA so that a developer can add the diagnostic VTI javadoc to the public api. Thanks.
                
> 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
>
> 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