RFR: 8173943: Change error reporting of LauncherHelper to include actual Error class name

Alan Bateman Alan.Bateman at oracle.com
Mon Feb 6 10:40:01 UTC 2017



On 06/02/2017 03:22, Ramanand Patil wrote:
> :
>
> 2. After Fixing JDK-8167063:
> Error: Unable to load main class pkgB.ClassB from module mod.b
> superclass access check failed: class pkgB.ClassB (in module mod.b) cannot access class pkgA.ClassA (in module mod.a) because module mod.a does not export pkgA to module mod.b
>
> [Here the complete stacktrace was removed to be consistent with the error handling mechanism of LauncherHelper, where only the important error message is printed and the complete stack trace is shown in diagnostic ("-Xdiag") mode.]
>
> 3. After fixing the current Bug( JDK-8173943 ):
> Error: Unable to load main class pkgB.ClassB from module mod.b
> java.lang.IllegalAccessError: superclass access check failed: class pkgB.ClassB (in module mod.b) cannot access class pkgA.ClassA (in module mod.a) because module mod.a does not export pkgA to module mod.b
>
This looks okay, I hadn't noticed that the error type has been lost with 
the changes in JDK-8167063.

-Alan


More information about the core-libs-dev mailing list