-
Notifications
You must be signed in to change notification settings - Fork 83
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
JUnit Plug-in tests cannot be started if an older target platform is used #733
Comments
From this error message I assume that you start your test-runtime with a JRE below Java-11? As a workaround it would probably be sufficient to add |
Thanks @HannesWell I will give this a try. |
The issue is also present with a Java 17 runtime, I just had this issue with the second client. Adding |
With a Java-17 runtime probably the first Missing requirement remains:
I see options:
The first option is difficult to ensure with confidence since we (at least currently) have no tests for that and the question would be which would be the oldest supported version. Therefore option one would actually be the saver and cleaner one. |
I agree with this assessment. The bound was only changed for "our safety and comfort" but while it might be safe, it turns out not to be comfortable... |
I just created #765 to lower it. |
Awesome @HannesWell this will be very useful for my clients (once they upgrade, I don't think they are willing to use I-Builds). |
If I use
PDE plug-in tests will not work with the following error message:
If I switch to a recent release, like I can start JUnit Plug-in tests.
Full target platform:
Is it expected that the target platform influences the ability to execute JUnit Plug-in tests?
The text was updated successfully, but these errors were encountered: