New release DefaultFileSystemProviders

[Michael Hall]

> On Jul 30, 2021, at 9:36 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> On 30/07/2021 00:00, Michael Hall wrote:
>> Correction non-modular exploded works
>> 
>> java 18 exploded works
>> /usr/libexec/java_home -v 18 --exec java -cp .:macnio2 -Djava.security.manager -Djava.security.policy=all.policy -Djava.nio.file.spi.DefaultFileSystemProvider=us.hall.trz.osx.MacFileSystemProvider org.test.Test
>> WARNING: A command line option has enabled the Security Manager
>> WARNING: The Security Manager is deprecated and will be removed in a future release
>> us.hall.trz.osx.MacFileSystem at 60e53b93
>> us.hall.trz.osx.MacFileSystemProvider
>> 
>> java 17 exploded works
>> /usr/libexec/java_home -v 17 --exec java -cp .:macnio2 -Djava.security.manager -Djava.security.policy=all.policy -Djava.nio.file.spi.DefaultFileSystemProvider=us.hall.trz.osx.MacFileSystemProvider org.test.Test
>> WARNING: A command line option has enabled the Security Manager
>> WARNING: The Security Manager is deprecated and will be removed in a future release
>> us.hall.trz.osx.MacFileSystem at 511d50c0
>> us.hall.trz.osx.MacFileSystemProvider
>> 
>> Non-exploded, or jar’d, is probably still https://bugs.openjdk.java.net/browse/JDK-8263940
> Yes, the exploded case should be okay. However, if java.nio.file.spi.DefaultFileSystemProvider specifies a class in a JAR file that is on the class path or module path then you'll run into this issue.  Setting the security manager on the command line will trigger this occur at VM startup.
> -Alan

Thanks for explaining the conditions. I will hold off on additional testing for now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/nio-dev/attachments/20210730/ccead2f7/attachment-0001.htm>