My understanding is that the Aqua L&F classes are already inaccessible
if there's a SecurityManager so its not a completely new thing.
Whilst there may be ways around the JDK9 restrictions, what internal
Aqua APIs do you need
to customise ? And how do you deliver those customisations ?
We are already looking at finding ways to expose some com.apple APIs in
a supported way as Java APIs.
Perhaps something in Aqua can be fixed, or perhaps exposed - perhaps
being a key word.
Note that bundling a JRE is not the same thing as building your own &
bundling.
I expect most applications will want to work with a pre-built Oracle JDK
which will hide internal APIs.
Perhaps
On 5/15/2015 12:09 PM, Alan Snyder wrote:
If my understanding is correct, the classes for several JDK specific L&Fs
(Aqua, GTK, and Windows) will become inaccessible to applications in JDK9. Is this
true?
I am concerned about the impact of this change for the Aqua look and feel,
which historically has lagged behind the platform UI and continues to do so
(although progress has been made) and for which both small and large
customizations have been written. Blocking access to the Aqua look and feel
classes will make such customizations much more difficult, possibly even
impossible if native code is involved.
While I understand the desire to protect applications from depending upon JDK
specific code, the benefit of this restriction seems small. After all, how many
JDK implementations are there for desktop applications on OS X? The current OS
X application architecture bundles a JRE in each application, so JDK changes
will not break installed applications.
