add `--add-opens` option to solve InaccessibleObjectException #101

KengoTODA · 2017-01-08T11:09:14Z

New Java9 package oracle-java9-installer=9b149+9b149arm-1~webupd8~0 was released at Jan/4th, and it introduced a build error to spotbugs.

This pull-request solves it by adding --add-opens option to GRADLE_OPTS envvar.

…9 b149

KengoTODA · 2017-01-08T11:14:46Z

This pull-request is still unstable, we have another build failure as follows.
Currently I cannot set up Java9 environment in local due to network instability. If you have time, please try to reproduce this problem to find solution.

FAILURE: Build failed with an exception.

* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------

FAILURE: Build failed with an exception.

* What went wrong:
java.lang.ExceptionInInitializerError (no error message)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------

FAILURE: Build failed with an exception.

* What went wrong:
java.lang.ExceptionInInitializerError (no error message)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

	at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
	at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:151)
	at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:134)
	at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:203)
	at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:125)
	at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:127)
	at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:81)
	at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
	at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:244)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174)
	at org.gradle.launcher.Main.doAction(Main.java:33)
	at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:538)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
	at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:538)
	at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:31)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:108)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

KengoTODA · 2017-01-09T14:59:23Z

Posted a question to Gradle forum:
https://discuss.gradle.org/t/gradle-with-java9-b149-throws-exceptionininitializererror/21068

KengoTODA · 2017-01-14T12:57:00Z

.travis.yml


 install:
  - mkdir -p deps
-  - if [[ ! -e deps/eclipse.tar.gz ]]; then wget http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.6.2-201102101200/eclipse-SDK-3.6.2-linux-gtk-x86_64.tar.gz -O deps/eclipse.tar.gz; fi


3.6.2 is now 404 not found again...

KengoTODA · 2017-01-14T12:58:17Z

I fixed one of known problems, however Java9 still have another problems. I'll continue investigation to solve.

KengoTODA · 2017-01-14T14:04:26Z

This is the current problem:

FAILURE: Build failed with an exception.
* Where:
Settings file '/home/travis/build/spotbugs/spotbugs/settings.gradle' line: 2
* What went wrong:
A problem occurred evaluating settings 'spotbugs'.
> No signature of method: java.io.File.exists() is applicable for argument types: () values: []
  Possible solutions: wait(), equals(java.lang.Object), wait(long), is(java.lang.Object), with(groovy.lang.Closure), print(java.io.PrintWriter)

I guess jigsaw makes java.io.File inaccessible.

http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-December/010456.html

KengoTODA · 2017-01-15T03:13:55Z

Next problem is that, eclipse command exists with exit value 136.
I confirmed that all of Eclipse 3.6 ~ 4.2 have the same problem. I also confirmed that non-container based environment has the same problem.

:eclipsePlugin:generateCandidateP2MetadataJava 
HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
(Eclipse:4647): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(Eclipse:4647): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): GLib-GObject-CRITICAL **: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:4647): GLib-GObject-WARNING **: value "TRUE" of type 'gboolean' is invalid or out of range for property 'visible' of type 'gboolean'
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): GLib-GObject-CRITICAL **: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:4647): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(Eclipse:4647): Gdk-CRITICAL **: IA__gdk_pango_context_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_font_description: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_base_dir: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_language: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_new: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_text: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_attributes: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_alignment: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_ellipsize: assertion 'PANGO_IS_LAYOUT (layout)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_single_paragraph_mode: assertion 'PANGO_IS_LAYOUT (layout)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_width: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_get_extents: assertion 'layout != NULL' failed
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_icon_size_lookup_for_settings: assertion 'GTK_IS_SETTINGS (settings)' failed
(Eclipse:4647): Gtk-WARNING **: Invalid icon size 6
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_icon_theme_load_icon: assertion 'GTK_IS_ICON_THEME (icon_theme)' failed
(Eclipse:4647): Gtk-WARNING **: Error loading theme icon 'dialog-error' for stock: 
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_icon_size_lookup_for_settings: assertion 'GTK_IS_SETTINGS (settings)' failed
(Eclipse:4647): Gtk-WARNING **: /build/gtk+2.0-KsZSEA/gtk+2.0-2.24.23/gtk/gtkstyle.c:2358: invalid icon size '6'
(Eclipse:4647): Gtk-CRITICAL **: IA__gtk_style_render_icon: assertion 'pixbuf != NULL' failed
(Eclipse:4647): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:4647): Gdk-CRITICAL **: IA__gdk_pango_context_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_font_description: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_base_dir: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_language: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_new: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_text: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_alignment: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_ellipsize: assertion 'PANGO_IS_LAYOUT (layout)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_single_paragraph_mode: assertion 'PANGO_IS_LAYOUT (layout)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_wrap: assertion 'PANGO_IS_LAYOUT (layout)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_width: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_get_extents: assertion 'layout != NULL' failed
(Eclipse:4647): Gdk-CRITICAL **: IA__gdk_pango_context_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_font_description: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_base_dir: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_context_set_language: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_new: assertion 'context != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_text: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_get_extents: assertion 'layout != NULL' failed
(Eclipse:4647): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:4647): Gdk-CRITICAL **: IA__gdk_screen_get_width: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Gdk-CRITICAL **: IA__gdk_screen_get_width: assertion 'GDK_IS_SCREEN (screen)' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_set_width: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_get_extents: assertion 'layout != NULL' failed
(Eclipse:4647): Pango-CRITICAL **: pango_layout_get_line_count: assertion 'layout != NULL' failed
FAILED

KengoTODA · 2017-01-15T06:05:12Z

I enabled Xvfb, it can solve warnings & errors but it faced build timeout.

https://travis-ci.org/KengoTODA/spotbugs/jobs/192049528

I think it's better to use oraclejdk8 to build & kick eclipse, and use oraclejdk9 only to run tests.

KengoTODA · 2017-01-18T15:21:40Z

Current problem: we cannot load java/lang/Object.class by class loader in findbugs/src/main/java/edu/umd/cs/findbugs/classfile/impl/ClassPathBuilder.java due to: http://openjdk.java.net/projects/jigsaw/spec/issues/#ClassFilesAsResources

Above spec page says that this problem is already resolved, but I found no solution for now (I added following JVM arguments as trial).

      '--add-exports', 'java.base/java.lang=ALL-UNNAMED',
      '--add-reads', 'java.base=ALL-UNNAMED'

henrik242 · 2017-01-21T16:10:32Z

I have forced using an older jdk9 to make it build again in #105, while we try to figure out how to solve this.

KengoTODA · 2017-09-21T13:45:17Z

Use #393 to build with JDK 9.

add --add-opens option to solve InaccessibleObjectException w/ Java…

f3dbcc8

…9 b149

KengoTODA added help wanted Java-9 WIP labels Jan 8, 2017

change YAML format to make it more intuitive

0d2d364

KengoTODA mentioned this pull request Jan 8, 2017

Reproduce reported problem, and solve it by upgrading BCEL to 6.1 #69

Merged

KengoTODA and others added 4 commits January 12, 2017 21:07

diable Gradle daemon

1c5bae4

add oracle-java9-set-default package

5a9050f

Fix yams format problem

205c3c7

solve ExceptionInInitializerError by --add-opens option

3798c10

KengoTODA commented Jan 14, 2017

View reviewed changes

KengoTODA self-assigned this Jan 14, 2017

KengoTODA added 2 commits January 15, 2017 11:01

add recommended option by Java9 mailing list

458172c

http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-December/010456.html

switch back to eclipse 3.6

c37d4eb

KengoTODA added a commit to KengoTODA/spotbugs that referenced this pull request Jan 15, 2017

temporally drop build with java9, it will be back in spotbugs#101

d9d37f1

KengoTODA mentioned this pull request Jan 15, 2017

temporally drop build with java9, it will be back in #101 #103

Merged

KengoTODA added 3 commits January 18, 2017 21:24

use Java9 only when run JUnit test

407eb7f

add missing protocol in URL of eclipse

8bb9005

move configuration from root project to :findbugs project

ca5b110

henrik242 pushed a commit that referenced this pull request Jan 21, 2017

temporally drop build with java9, it will be back in #101

5e50424

henrik242 mentioned this pull request Jan 21, 2017

Reintroduce jdk9 and lock to latest known working version #105

Merged

KengoTODA mentioned this pull request Mar 7, 2017

Cannot run FindBugs on JDK9: "Resource not found: java/lang/Object.class" #148

Closed

KengoTODA mentioned this pull request Sep 19, 2017

Consume final ASM 6 #373

Closed

KengoTODA closed this Sep 21, 2017

KengoTODA deleted the fix-java9-error branch September 21, 2017 13:46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

add `--add-opens` option to solve InaccessibleObjectException #101

add `--add-opens` option to solve InaccessibleObjectException #101

KengoTODA commented Jan 8, 2017

KengoTODA commented Jan 8, 2017

KengoTODA commented Jan 9, 2017

KengoTODA Jan 14, 2017

KengoTODA commented Jan 14, 2017 •

edited

KengoTODA commented Jan 14, 2017

KengoTODA commented Jan 15, 2017

KengoTODA commented Jan 15, 2017

KengoTODA commented Jan 18, 2017

henrik242 commented Jan 21, 2017 •

edited

KengoTODA commented Sep 21, 2017

add --add-opens option to solve InaccessibleObjectException #101

add --add-opens option to solve InaccessibleObjectException #101

Conversation

KengoTODA commented Jan 8, 2017

KengoTODA commented Jan 8, 2017

KengoTODA commented Jan 9, 2017

KengoTODA Jan 14, 2017

Choose a reason for hiding this comment

KengoTODA commented Jan 14, 2017 • edited

KengoTODA commented Jan 14, 2017

KengoTODA commented Jan 15, 2017

KengoTODA commented Jan 15, 2017

KengoTODA commented Jan 18, 2017

henrik242 commented Jan 21, 2017 • edited

KengoTODA commented Sep 21, 2017

add `--add-opens` option to solve InaccessibleObjectException #101

add `--add-opens` option to solve InaccessibleObjectException #101

KengoTODA commented Jan 14, 2017 •

edited

henrik242 commented Jan 21, 2017 •

edited