db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3780) Run junit tests with -Dfile.encoding="UTF-16" to expose encoding issues and analyze failures
Date Fri, 18 Jul 2008 18:44:31 GMT

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

Kathey Marsden updated DERBY-3780:
----------------------------------

    Attachment: derby-3780_diff.txt

Attached is a patch to fix the test encoding issues with
jdbc4/ClobTest.java
jdbcapi/LargeDataLocksTest.java
jdbcapi/BlobClob4BlobTest.java
tools/ImportExportTest.java

> Run junit tests with -Dfile.encoding="UTF-16" to expose encoding issues and analyze failures
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3780
>                 URL: https://issues.apache.org/jira/browse/DERBY-3780
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: derby-3780_diff.txt, ReadEncodedFile.java, suites_all_utf16.txt
>
>
> Wth sun jkd 1.5 and 1.6 you can run JUnit tests with -Dfile.encoding="UTF-16" to help
expose encoding issues with Derby and tests.    Run suites.All and analyze failures.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message