-
Notifications
You must be signed in to change notification settings - Fork 60
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
[numbers] support JUnit 5 tests #47
Conversation
I think the recommended way is to use the JUnit Bill of Materials which contains all the versions which work together:
You can see what it bundles on Maven repository org.junit:junit-bom:5.4.2. I am not sure how it works with the legacy junit 4 dependency. I would try deleting that from the POM and just trying with the vintage engine dependency. |
26580cf
to
f8a8ff1
Compare
@aherbert what about this iteration? As I wrote in my original email, I don't know maven that well. (also, you're allowed to push to this branch if it'd help) |
Looks fine. Let's see if Travis can run all the tests. |
f8a8ff1
to
fccc6fe
Compare
Updated. Travis failed previously on coveralls related errors but not on the core tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good now
Pushed as fccc6fe. Hope I did that right. |
I've pulled master and the changes are there. Downstream PRs for the switch to JUnit 5 should all be OK. |
actually see 6bcc6d9 |
No description provided.