<AWT Dev> Java 9 on OS X internal API com.apple.eio.FileManager
mik3hall at gmail.com
Tue Sep 26 21:39:06 UTC 2017
> On Sep 26, 2017, at 4:22 PM, mandy chung <mandy.chung at oracle.com> wrote:
> 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…
>> 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.
All right. If RFE is in fact the correct way to go in resolving the status of the code I will try to figure out how to do that.
More information about the awt-dev