On 16/12/2014 06:07, joe darcy wrote:
Hello,
Please review the next step of suppressing the deprecation warnings
the client libraries, this time in windows-specific desktop code:
JDK-8067092: Suppress windows-specific deprecation warnings in the
java.desktop module
On 12/16/2014 3:15 AM, Alan Bateman wrote:
On 16/12/2014 06:07, joe darcy wrote:
Hello,
Please review the next step of suppressing the deprecation warnings
the client libraries, this time in windows-specific desktop code:
JDK-8067092: Suppress windows-specific deprecation warnings in
Thanks for the review.
Just one more fix to review to finish suppressing the deprecation
warnings in the desktop module; please also see the review request for
JDK-8067086: Suppress mac-specific deprecation warnings in the
java.desktop module:
Stop using them and replace them with new package private methods and a
cross-package accessor (similar to the SurfaceManager.ImageAccessor
pattern)? What are the technical constraints preventing this?
I think the getPeer() method used to be used by AWT applications to tell
if an app was on
Yes .. no technical constraint there.
Although I was pondering going further and seeing if we can actually remove
the public method java.awt.peer.Peer Component.getPeer()
since with the module system the peer package is not accessible and this
is then even weirder than it is now .. as it
On 16/12/2014 18:29, Phil Race wrote:
Yes .. no technical constraint there.
Although I was pondering going further and seeing if we can actually
remove
the public method java.awt.peer.Peer Component.getPeer()
since with the module system the peer package is not accessible and this
is then even
Hello,
Please review the next step of suppressing the deprecation warnings the
client libraries, this time in windows-specific desktop code:
JDK-8067092: Suppress windows-specific deprecation warnings in the
java.desktop module
http://cr.openjdk.java.net/~darcy/8067092.0/
Thanks,
