db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-323) Locale problem in test of derby
Date Tue, 31 May 2005 15:00:52 GMT
     [ http://issues.apache.org/jira/browse/DERBY-323?page=comments#action_66624 ]
     
Tomohito Nakayama commented on DERBY-323:
-----------------------------------------

There exists way to escape problem in Windows.
We can change locale of windows from control panel.
After changed to US locale, test of derby works correctly.

see http://article.gmane.org/gmane.comp.apache.db.derby.devel/4658

In Japanese localed Windows, this configuration is at , 
コントロールパネル>地域と言語のオプション

> Locale problem in test of derby
> -------------------------------
>
>          Key: DERBY-323
>          URL: http://issues.apache.org/jira/browse/DERBY-323
>      Project: Derby
>         Type: Bug
>   Components: Test
>  Environment: Japanese localed Windows using cygwiin
>     Reporter: Tomohito Nakayama

>
> Many of derbyall fails at Japanese localed Windows when environment corresponding derbyLocale_JP.jar
exists in CLASSPATH.
> Almost all of derby_all was failed because all result message was generated in 
> Japanese , and that was different from master file.
> I tried next configuration ...
> conf_0:Exclude derbyLocale_jp.jar
> conf_1:Add option "-Duser.language=en -Duser.country=US"
> conf_2:Add option "-Djvmflags=-Duser.language=en -Duser.country=US"
> conf_3:Defiine environment variable _JAVA_OPTIONS=:-Duser.language=en -Duser.locale=us
> conf_4:Defiine environment variable LC_CTYPE:en_US
> conf_0 works well on derbyall suite but some of derbynetclientmats/derbynetmats in derbyall
suite was failed. Network module seems to have localed message in other resource.
> conf_1 works on derbynetclientsmats suite, but same configuration for derbyall suite
does not work at all.
> conf_2 does not work on derbynetclientsmats suite.
> conf_3 seems to work for locale problem but  "Picked up _JAVA_OPTIONS:" message cause
error in test.
> conf_4 does not works ...
> Now conf_0 seems to be reasonable method now.
> I think conf_3 may be reasonable direction to modify test suite. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message