[jira] [Commented] (DERBY-5950) PlanExporter and SignatureChecker don't appear in the list of tools supported by derbyrun.

["Bryan Pendleton (JIRA)" <ji...@apache.org>]

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

Bryan Pendleton commented on DERBY-5950:
----------------------------------------

Hello Yun,

I had no problems building with your change and I was able to test that I could:
a) See the information about SignatureChecker and PlanExporter in the help, and
b) Invoke PlanExporter via -jar derbyrun.jar PlanExporter

I notice, in the 'svn_status.txt' that you attached with your patches, that you
had modifications to the "jar.lastcontents" files.

When I built, I did not need to make any modifications to the "lastcontents" files,
but I wanted to check -- are the changes that you had to make related to the
problem that we saw with DERBY-6857? That is, if you update to the head of
trunk, do your "lastcontents" modifications disappear?

I am intending to commit this patch, because I think it is ready to go, but it
would be nice if you could verify that the "lastcontents" changes are not needed.

> PlanExporter and SignatureChecker don't appear in the list of tools supported by derbyrun.
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5950
>                 URL: https://issues.apache.org/jira/browse/DERBY-5950
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.10.1.1
>            Reporter: Rick Hillegas
>            Assignee: Yun Fang
>              Labels: derby_triage10_11
>         Attachments: run.java.diff, svn_status.txt, toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for derbyrun does not mention PlanExporter or SignatureChecker. It should.
> java -jar trunk/jars/sane/derbyrun.jar
> Usage:
> java -jar derbyrun.jar ij [-p propertiesfile] [sql script]
> java -jar derbyrun.jar sysinfo [-cp ...] [-cp help] 
> java -jar derbyrun.jar dblook [args] (or no arguments for usage)
> java -jar derbyrun.jar server [args] (or no arguments for usage)
> Note that SignatureChecker can still be invoked via derbyrun. However, PlanExporter can't:
> java -jar trunk/jars/sane/derbyrun.jar SignatureChecker
> Usage if running on J2SE:
>  
>  	java org.apache.derby.tools.SignatureChecker  connectionUrlToDatabase
>  
> Usage if running on J2ME:
>  
>  	java org.apache.derby.tools.SignatureChecker databaseName
> java -jar trunk/jars/sane/derbyrun.jar PlanExporter
> Usage:
> java -jar derbyrun.jar ij [-p propertiesfile] [sql script]
> java -jar derbyrun.jar sysinfo [-cp ...] [-cp help] 
> java -jar derbyrun.jar dblook [args] (or no arguments for usage)
> java -jar derbyrun.jar server [args] (or no arguments for usage)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)