java.io.File#toPath() on Windows doesn't understand "NUL:" (null device)?

[Jaikiran Pai]

On 17/03/21 3:16 pm, Jaikiran Pai wrote:
>
> On 17/03/21 3:10 pm, Jaikiran Pai wrote:
>> Hello Alan,
>>
>> On 17/03/21 2:45 pm, Alan Bateman wrote:
>>> On 17/03/2021 08:21, Jaikiran Pai wrote:
>>>> :
>>>>
>>>> I can confirm that using "NUL" or "nul" work fine in the above code,
>>>
>>> I don't know the context for your question 
>>
>> ...
>>
> FWIW - that bug report states that they ran into this even when using 
> "nul" and not just "nul:". So there might be something more going on 
> here and am just waiting to see if they can provide us a build file to 
> reproduce this issue.

I received some inputs on that Ant bugzilla issue. Based on that, I was 
able to reproduce the exception and IMO it's a bug in 
Files.newOutputStream() API. I have opened 
https://bugs.openjdk.java.net/browse/JDK-8263898 with the relevant 
details. I considered this a bug and took the liberty of opening that 
JBS issue because as I note in that issue, this only happens 
specifically when TRUNCATE_EXISTING (default) option gets used against 
"nul" on Windows.


-Jaikiran