-
Notifications
You must be signed in to change notification settings - Fork 52
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
Illegal reflective access warning on JDK11 #226
Comments
Thanks a lot @moovida for reporting this issue. Currently AssertJ Swing still requires Java 8. Now we know the term "or higher" ends at least with Java 11, so we have to work on that. The exception above shows that the Realistically this issue might be open for a while ... :/ |
Hi @croesch , yes, I ran the tests without that one and they all passed. |
Hi @croesch , I am on ubuntu with :
and using:
I am not sure about the clicking thing though. Is there something I can do to check this? |
Illegal reflective access in fest-reflect also mentioned in #237 |
Hi there! Is anyone working on this issue? It is a real blocker for us... |
I don't think so, contributions welcome ;-) |
Hi, This is the error: The test was simple: @test There were other issues before getting here (I needed to reimport the junit-platform-commons). Maybe you should change in the README. "or higher" for java11. At least for the Environment variables :) |
The code it's running seems like it's just trying to get the current repaint manager: Object repaintManager = method("appContextGet").withReturnType(Object.class).withParameterTypes(Object.class)
.in(SwingUtilities.class).invoke(RepaintManager.class); Whereas in the public API there is this: RepaintManager repaintManager = RepaintManager.currentManager((Component) null); There's no |
By checking OpenJDK commit history, it have already existed from a start of OpenJDK project, which has "initial load" commit message. It means JDK 7 and later has it. |
Hi, on java 11 I get the following test warnings due to illegal reflective access:
The text was updated successfully, but these errors were encountered: