On 9/26/17 2:10 PM, Michael Hall wrote:
The example below seems to be something that would be better
off in java.nio.files and so would not have been appropriate for the
desktop JEP and you may want to file an RFE against core-libs/java.nio
I would agree this might not be the best fit to AWT/Desktop. It is
however where jdeps indicates it should be.
The migration guide…
https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-3A71ECEF-5FC5-46FE-9BA9-88CBFCE828CB
suggests you first run jdeps against your code to be sure there are no
internal api’s that will no longer be supported.
FileManager as I indicated is flagged as a java.desktop internal api.
JDK internal API (java.desktop)
You might want to see that this is changed so you don’t get asked by
others in the future what should be the java.desktop replacement.
com.apple.eio is encapsulated in java.desktop module. jdeps correctly
reports access to com.apple.eio.FileManager as an internal API.
Like Phil said, the best way is to file a RFE to describe the
functionality that com.apple.eio.FileManager you depend on and no public
API providing that in the platform.
Mandy
