Replacing default FileSystemProvider

Michael Hall mik3hall at gmail.com
Thu Mar 25 12:20:41 UTC 2021



> On Mar 25, 2021, at 6:40 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> On 24/03/2021 14:06, Michael Hall wrote:
>> :
>> 
>> Double checking the bug report seems to show that jar or modular jar are the only not exploded options(?) I was hoping for a workaround that didn’t require exploded but for now I guess I’ll settle for that.
>> 
> I think the bug is specified to the case that the default file system provider is deployed in a JAR file on the class path. Hopefully that will be fixed soon. The other cases, where the default file system provider is exploded on the class path, or deployed as a module on the module path (exploded or modular JAR) should not be impacted by the bug.
> 
> -Alan

It seemed to occur for me with a modular jar. But I haven’t done anything modular yet so may not of done it correctly. I will look further into the test cases you indicated. Otherwise I will watch the bug for resolution.

Thanks again for the time. 




More information about the nio-dev mailing list