[
https://issues.apache.org/jira/browse/DERBY-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-3737:
-----------------------------
Attachment: DERBY-3737.zip
DERBY-3737.stat
DERBY-3737.diff
Attaching DERBY-3737.diff, DERBY-3737.stat, and DERBY-3737.zip, with changes to
the Tools and Reference manuals to document SignatureChecker. New topics are:
"SignatureChecker", ctoolssigcheck.dita
"Using SignatureChecker", ctoolsusingsigcheck.dita
Existing topics affected are:
"Purpose of this document", ctoolspre11181.dita (I also decided to change
"database class loading utilities" to "jar file utilities" here and elsewhere,
since that seems a more accurate description -- it's what they're called in the
section that describes them. Does this make sense?)
"How this guide is organized", ctoolspre23947.dita (with extra fixes to remove
a duplicated link, to use appropriate fonts, and to provide the same kind of
info for each tool)
"Overview", ctoolsijtools30948.dita, which contains another list of all the
tools (I also changed this topic to make it more consistent in the information
it provides for each tool)
"Environment setup and the Derby tools", ctoolsijtools37363.dita (I'm guessing
that SignatureChecker can be used in either an embedded or a client/server
environment, but I don't know -- can it?)
"Argument matching", rrefsqljargmatching.dita -- added reference to Tools guide
Thanks for any comments!
> 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: 10.5.1.1
> 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.
