This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | reflect.InaccessibleObjectException: Unable to make member of class sun.awt.im.InputContext accessible: module java.desktop does not export sun.awt.im to unnamed module @4a00808f | ||
---|---|---|---|
Product: | platform | Reporter: | Jiri Prox <jiriprox> |
Component: | Launchers&CLI | Assignee: | Libor Fischmeistr <lfischmeistr> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | ftsiang, jiriprox, mbalin |
Priority: | P2 | Keywords: | JDK_9 |
Version: | 8.2 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 223671 |
Attachments: |
stacktrace
stacktrace |
Description
Jiri Prox
2016-04-21 13:30:15 UTC
Created attachment 159377 [details]
stacktrace
Created attachment 159378 [details]
stacktrace
Opening GUI designer
This is thrown in many cases: for example opening output window, browsing project structure .... There seems to be a difference when using dev build of JDK9 supp (with addExports in launchers) on top of JDK9 vs running own build with command line switches as specified here: http://wiki.netbeans.org/JDK9Support#Linux Testing with ClientEditor sample. Using JDK9 build 201604210404 from download page - various exceptions about unexported packages to NB modules. Running JDK9 build built from sources with command line switches like ./netbeans --jdkhome /home/mb/jdk9-ea-b113 -J-XaddExports:java.desktop/sun.awt=ALL-UNNAMED -J-XaddExports:java.base/jdk.internal.jrtfs=ALL-UNNAMED -J-XaddExports:java.desktop/java.awt.peer=ALL-UNNAMED -J-XaddExports:java.desktop/com.sun.beans.editors=ALL-UNNAMED -J-XaddExports:java.desktop/sun.awt.im=ALL-UNNAMED -J-XaddExports:java.desktop/com.sun.java.swing.plaf.gtk=ALL-UNNAMED -J-XaddExports:java.management/sun.management=ALL-UNNAMED No illegal access issue at all. Looks like problem is with launcher and passing addExports to JVM. Works with newer JDK 9 build b114. Closing Sorry, wrong issue. |