Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please document how to build with later versions of jdk and openjfx #56

Open
daveyostcom opened this issue Feb 9, 2020 · 2 comments
Open

Comments

@daveyostcom
Copy link

I start with this, which works:

cd /tmp
git clone --depth=1 https://github.com/JonathanGiles/scenic-view.git
cd scenic-view
gradlew build
gradlew jlink
build/scenicview/bin/scenicView

Then I run my app with java -javaagent:/tmp/scenic-view/build/scenicview/lib/scenicview.jar

My app complains thus:

Exception in thread "JavaFX Application Thread" java.lang.IllegalAccessError: superclass access check failed: class com.sun.javafx.sg.prism.web.NGWebView (in unnamed module @0x33b37288) cannot access class com.sun.javafx.sg.prism.NGGroup (in module javafx.graphics) because module javafx.graphics does not export com.sun.javafx.sg.prism to unnamed module @0x33b37288

What do I need to do, exactly?

Is this happening because my app is running on java 13 (build 13+33) using javafx 13.0.2 ?

@Groostav
Copy link

Groostav commented Feb 23, 2021

similar, I've got complaints about embedded swing components, webview, amongst others. Once all the exceptions are gone (which I achieved by dumping a bunch of javafx jars onto my classpath) my application is still not appearing in the scenicview window.

This tool was instrumental to us building for java-8, since then we ported to java 13, and I cant describe how frustrating it is not to have this fabulous tool in my toolbelt anymore.

@Groostav
Copy link

Groostav commented Mar 3, 2021

I've also tried building this for java 13, but gradle wont run on java 13. I guess the thing I'm being frustraited by is my lack of understanding for the IPC hooks? I don't understand why a jar built for java 11 wouldn't properly instrument a java 13 application when run with -javaagent. It seems like there's some fairly brittle IPC devices here that I need more understanding of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants