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-3737) Document the new SignatureChecker lint tool in the Tools Guide
Date Thu, 28 May 2009 13:25:45 GMT

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

Kim Haase resolved DERBY-3737.

       Resolution: Fixed
    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Thanks for making the release note so clear, Rick -- it made the documentation work very easy.

Committed patch DERBY-3737.diff to documentation trunk at revision 779589. 
Merged to 10.5 branch at revision 779597. 

> 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
>             Fix For:,
>         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