[
https://issues.apache.org/jira/browse/LUCENE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614842#comment-14614842
]
Ramkumar Aiyengar commented on LUCENE-6563:
-------------------------------------------
I see why we shouldn't modify the internal prop -- it sounded hacky to begin
with, but I still think our tests shouldn't fail for some supported locale on a
supported OS (I was able to reproduce this on the latest Ubuntu on my laptop).
To the best of my knowledge, Lucene doesn't need non-ASCII file names for
itself -- so if we are not able to create non-ASCII filenames to begin with,
shouldn't the mock filesystem not try to use them? That way we continue to test
that if the OS was able to create non-ASCII parent directories, Lucene should
continue to work fine, but that shouldn't be a requirement for Lucene per se.
> sun.jnu.encoding to match file.encoding system property
> (MockFileSystemTestCase.testURI)
> ----------------------------------------------------------------------------------------
>
> Key: LUCENE-6563
> URL: https://issues.apache.org/jira/browse/LUCENE-6563
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Christine Poerschke
> Assignee: Dawid Weiss
> Priority: Minor
>
> {{ant test -Dtestcase=TestVerboseFS -Dtests.method=testURI
> -Dtests.file.encoding=UTF-8}} fails (for example) with 'Oracle Corporation
> 1.8.0_45 (64-bit)' when the default {{sun.jnu.encoding}} system property is
> (for example) {{ANSI_X3.4-1968}}
> [details to follow]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
