> On Sep 26, 2017, at 12:20 PM, Phil Race <philip.r...@oracle.com> wrote:
> 
> I didn't do the work here so I am answering as best I can.
> FileManager is not directly exposed but is used in implementing
> a couple of APIs on the java.awt.Desktop class.

This will not help developers who used this in their applications. If there are 
no direct Desktop replacements.

> 
> If you think some important use case that is appropriate there is
> missed then you can file an RFE on that.

I think this was discussed and this class mentioned on a couple different 
occasions. 
I can only assume the decision was to simply drop support without replacement.
I’m not sure an RFE would reverse that decision.

> 
> 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
 
<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.

> 
> Unfortunately, I can't answer licensing questions for you.

I guess I will try to take a closer look at Classpath exception myself. I just 
browsed it and it seems to be GPL2. 
I will have to take a closer look at that to see what it entails so I can use 
it or offer it myself. 
It might be better if the jdk clean disowned it. I think I tried compiling 
against it and it was indicated to be in the java.desktop module but
not exported. Hence, unavailable to compile? (OS X Eclipse Java 9 seems all 
right with compiling it? javac failed).  
Possibly I can rename. Somehow I will try to offer it off of my GitHub project. 
Anyone who cares to use it, can get it there, if they know about it.

> 
> -phil.
> 


Thanks for the answer.


Reply via email to