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

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5950:
-

Who can help review this patch? thanks.

> 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)

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

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5950:
-

Hi Byran,

I am sure that I didn't modify the "jar.lastcontents" manually. I don't
know how those files was changed, maybe those were modified by ant build
process, which I will pay attention for that next time. Please go ahead.
thanks.

Best regards,
Yun

On Mon, Feb 1, 2016 at 7:17 AM, Bryan Pendleton (JIRA) 



> 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)

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

[Yun Fang (JIRA)]

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

Yun Fang updated DERBY-5950:

Attachment: run.java.diff
svn_status.txt
toolsmessages.properties.diff
toolsmessages_zh_CN.properties.diff

Here is the patchs for this bug and svn status info. The following tests is run:
1.
export LC_ALL=en_US.UTF-8
java -jar trunk/jars/sane/derbyrun.jar
2. 
java -jar trunk/jars/sane/derbyrun.jar PlanExporter
3. 
export LC_ALL=zh_CN.UTF-8
java -jar trunk/jars/sane/derbyrun.jar
4. 
java -jar trunk/jars/sane/derbyrun.jar PlanExporter

> 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)

[jira] [Commented] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5944:
-

Hi Bryan, the secretary of ASF,Craig L Russell, reply my email and notify me 
that my ICLA has been filed. Is this register process over now? 

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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

[jira] [Commented] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5944:
-

Under your hint, I also ran all the three testings. All of those are ok.

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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

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

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5950:
-

This bug is related another bug DERBY- 5944 that I am fixing, I think I can 
also fix this bug. So please help assign this bug to me. Thanks.

> 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
>  Labels: derby_triage10_11
>
> 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)

[jira] [Commented] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5944:
-

Hi Bryan, thank you for the reminder, I just had signed and emailed the ' 
Individual Contributor License Agreement' to secret...@apache.org. I believe I 
will register as an Apache contributor soon.

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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

[jira] [Issue Comment Deleted] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang updated DERBY-5944:

Comment: was deleted

(was: Hi Bryan, thank you for the reminder, I just had signed and emailed the ' 
Individual Contributor License Agreement' to secret...@apache.org. I believe I 
will register as an Apache contributor soon.)

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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

[jira] [Commented] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang commented on DERBY-5944:
-

Hi Bryan, thank you for the reminder, I just had signed and emailed the ' 
Individual Contributor License Agreement' to secret...@apache.org. I believe I 
will register as an Apache contributor soon.

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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

[jira] [Updated] (DERBY-5944) The hard-coded PlanExporter help message should be internationalized so that it can be translated

[Yun Fang (JIRA)]

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

Yun Fang updated DERBY-5944:

Attachment: MessageVetter.java.diff
toolsmessages_zh_CN.properties.diff
toolsmessages.properties.diff
PlanExporter.java.diff

Here is my changes for this defect. Because this defect is I18N related issue, 
it need to be contributed all of language translation for the properties, but I 
just only can make original english text and chinese translation, and I have no 
idea about other language version, maybe this is another issue ? Please help 
review and feedback. Thanks.

> The hard-coded PlanExporter help message should be internationalized so that 
> it can be translated
> -
>
> Key: DERBY-5944
> URL: https://issues.apache.org/jira/browse/DERBY-5944
> Project: Derby
>  Issue Type: Bug
>  Components: Localization, Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: MessageVetter.java.diff, PlanExporter.java.diff, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for PlanExporter is hard-coded in PlanExporter.printHelp(). 
> In contrast, other Derby tools use the message lookup logic for their help 
> messages. This means that for those other tools, on supported locales, users 
> see translated versions of the help messages. For PlanExporter, the help 
> message always appears in English. PlanExporter should use the message lookup 
> logic like the other tools do.



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