-
Notifications
You must be signed in to change notification settings - Fork 326
Depend on JUnit 6 instead of JUnit 5 #3560
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
base: main
Are you sure you want to change the base?
Conversation
|
There is a surprising number of JUnit 5 mentions, including even a quick fix action for adding JUnit 5 to the classpath... Probably for This PR so far doesn't touch any of those. |
2c93f7a to
ad11eb8
Compare
|
Running Fully summary: At least in JDT/PDE, this was usually an indicator of mixing JUnit 5 and 6 at runtime. It might be something else here. Such as JUnit 4 tests... Trying this: Results in: |
|
maybe this is a way too old tycho? |
Should I try updating to |
|
see #3509 we had a brief discussion to look into that someone after the current release (building milestones and releases is actually already beyond my cappa) |
|
the problem with tycho 5 is
what happens if use selects java 17 in wizard? should we have a fallback to old version. this also affecs junit 5/6 what should we offer the user. |
|
can you also check Jenkinsfile |
|
With |
We can always delay the JUnit 6 update for when Advantest is not in a rush, since the workaround is trivial. |
See: #3552