DefaultFileSystemProvider

[Michael Hall]

The recent fix for JDK-8263940 that just became available with the jdk18 ea appears to resolve about all remaining issues for my application.
I had some initial problems with this that seemed module related. I verified it worked with modular eliminated. 
I then noticed I was duplicating the provider code both in class path and module path. I had thought I just split out my Apple eio replacement and additions to a module. But the entire provider was there as well.

Given that I tried to see if it would run with the provider running strictly as a modular addition. It did not. 
Caused by: java.lang.Error: java.lang.ClassNotFoundException: us.hall.trz.osx.MacFileSystemProvider
Possibly something in my setup is wrong but if you are looking for complete coverage you might want to verify that running a class path app with a default provider included as modular works.

I am having some difficulty at the moment doing the split of class path jar provider and Apple eio replacement code to modular. But I am fairly certain I can run the app class path with modular as long as the provider isn’t included with the modular. So good enough for my purposes.