On Sat, 6 Nov 2021 16:59:12 GMT, Ichiroh Takiguchi <itakigu...@openjdk.org> wrote:
> In my understanding, sun.jnu.encoding property may be related file system > access. > Java may not be access to appropriate file. Yes, it's a JDK internal property with the charset name to use when decoding or encoding file names (not the file content). The issue in this PR is about what to do when starting in unsupported configurations. In the recent releases the JDK will typically NPE or fail with an exception. Since JEP 400 this no longer impacts the default charset because it is UTF-8. This moves the problem on to choosing a fallback for places in the JDK that use the value of native.encoding or sun.jnu.encoding. I think the only choices to either fail at startup or default to UTF-8 as proposed. ------------- PR: https://git.openjdk.java.net/jdk/pull/6282
