> On Nov 25, 2015, at 9:56 AM, Alan Bateman <[email protected]> wrote: > > If you feel strongly that the com.apple.eawt APIs should be exported in JDK 9 > then you need to read JEP 260 [1] and make a case for adding the Apple APIs > to the list.
I understand that knowing what impact a change will have is difficult to determine. I don’t think I could argue reversing that change solely on the basis of my own application. I can’t say how many applications it will affect. Probably most that have attempted to do any OS X customization. I myself am OK with these becoming supported going forward as part of the awt Desktop api’s. The question would be how many developers aren’t going to even be aware this has been done? I don’t have any estimate for that. My questions mostly concerned my own application. I was trying to figure out if I could get addExports to work without any other changes to my current application. Not modularizing. My use of addExports may of been incorrect for this use case. Unmodularized application using ‘internal’ api’s and trying to addExports around it. Does this work? What would be an example of the addExports for this situation? I not only wanted a free get out of jail card, I wanted a free lunch. If this doesn’t work I will probably try to isolate out the startup code that use the apple api’s and just modularize that. Or if worse comes to worse I’ll just kill the functionality that uses the api’s in order to test with jake until JEP 272 is in fact ready and I can change api's. Michael Hall
