On Jul 27, 2015, at 3:15 PM, Simon Nash si...@cjnash.com wrote:
It is hard to provide a definitive list of all the internal packages that
I need because the list tends to grow each time I use additional Swing
functionality in my application.
This does remind me of some code I had a while
I have recently discovered that applications will no longer be able
to access internal packages (sun.* and com.sun.*) in JDK 9. This is a
major problem for my application as it requires access to some internal
packages in order to work correctly.
In most cases, my need to access these internal
The jdeps tool bundled with current JDK 8 updates should help
you produced a definitive list - of your current uses.
A web page about jpdeps and current recommended replacements for
some internal APIs can be viewed at
https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
Phil Race wrote:
The jdeps tool bundled with current JDK 8 updates should help
you produced a definitive list - of your current uses.
Thanks for your quick reply. I will run this tool to check that my list
is complete and correct.
A web page about jpdeps and current recommended replacements
On 07/27/2015 03:56 PM, Simon Nash wrote:
Phil Race wrote:
The jdeps tool bundled with current JDK 8 updates should help
you produced a definitive list - of your current uses.
Thanks for your quick reply. I will run this tool to check that my list
is complete and correct.
A web page about
PS .. when you identify a workaround that you think
bears a resemblance to the required fix, you could
submit it as a patch. That way you won't lose track
of the issues and it has a good chance of being fixed
sooner.
-phil.
On 7/27/15 4:22 PM, Phil Race wrote:
On 07/27/2015 03:56 PM, Simon
On Jul 27, 2015, at 6:22 PM, Phil Race philip.r...@oracle.com
mailto:philip.r...@oracle.com wrote:
Will there be any way to access these if they are not public (for example,
by reflection)? If this is possible, I should be able to adapt my current
workaround code to run on JDK 9.
My
