RFR: 8357994: Use "stdin.encoding" for reading System.in with InputStreamReader/Scanner [client]

Volkan Yazici vyazici at openjdk.org
Mon Jun 2 08:23:56 UTC 2025


On Fri, 30 May 2025 21:21:56 GMT, Phil Race <prr at openjdk.org> wrote:

>> Passes the `Charset` read from the `stdin.encoding` system property while creating `InputStreamReader` or `Scanner` instances for `System.in`.
>> 
>> `stdin.encoding` is a recently added property for Java 25 in [JDK-8350703](https://bugs.openjdk.org/browse/JDK-8350703). Employing it throughout the entire code base is addressed by the parent ticket [JDK-8356893](https://bugs.openjdk.org/browse/JDK-8356893). JDK-8357994 this PR is addressing is a sub-task of JDK-8356893 and is concerned with only areas related to client libraries.
>
> This is the first I've heard of it but it makes absolutely zero sense here.
> The data transfer case is things like "drag and drop" between applications. You'll never see it coming from stdin
> And the editor kits will read FILES with some content you want to edit. No one will ever type it in.
> So in summary, withdraw this PR.

@prrace, thanks so much for the prompt feedback. Closing this PR and the associated JBS issue right away...

-------------

PR Comment: https://git.openjdk.org/jdk/pull/25543#issuecomment-2929387627


More information about the client-libs-dev mailing list