We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If the classpath does not contain OpenTest4J (e.g. you use JUnit 4 instead of JUnit 5) AssertJ 3.13.0 fails with:
3.13.0
java.lang.NoClassDefFoundError: org/opentest4j/MultipleFailuresError
A sample project to reproduce this issue: https://github.com/PascalSchumacher/assertj-3.13.0-requires-junit5-bug
The text was updated successfully, but these errors were encountered:
The hard dependency on OpenTest4J was introduced with this commit: d79423d#diff-4df7ee848542cb94166b422c1c3b05bd
Sorry, something went wrong.
Make dependency on OpenTest4J optional again (fixes assertj#1563).
df133ae
my bad :( this is not too serious IMO as people usually have opentest4j in their dependencies but let's try to fix that (if that's possible)
6a61bfc
AssertJ Core 3.13.1 is released with this fix.
No branches or pull requests
If the classpath does not contain OpenTest4J (e.g. you use JUnit 4 instead of JUnit 5) AssertJ
3.13.0
fails with:java.lang.NoClassDefFoundError: org/opentest4j/MultipleFailuresError
A sample project to reproduce this issue: https://github.com/PascalSchumacher/assertj-3.13.0-requires-junit5-bug
The text was updated successfully, but these errors were encountered: