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-3737) Document the new SignatureChecker lint tool in the Tools Guide
Date Wed, 27 May 2009 15:02:45 GMT

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

Rick Hillegas commented on DERBY-3737:

Hi Kim,

This looks great. I don't have any improvements to suggest.

1) I agree that "jar file utilities" is a better description than "database class loading

2) Yes, you can run the SignatureChecker on both embedded and client/server databases


> Document the new SignatureChecker lint tool in the Tools Guide
> --------------------------------------------------------------
>                 Key: DERBY-3737
>                 URL: https://issues.apache.org/jira/browse/DERBY-3737
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, SQL, Tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-3737.diff, DERBY-3737.stat, DERBY-3737.zip
> Add a section in the Tools Guide, describing how to use the SignatureChecker tool to
verify that all of the routines registered in a database actually match static Java methods
visible on the classpath. See DERBY-3652. The SignatureMatching.html webpage attached to that
issue describes what Derby's signature matching rules are. That issue also describes the SignatureChecker
tool, which was attached to the issue on June 23, 2008.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message