Bump JUnit to v5 and remove unused build elements #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abelsromero
force-pushed
the
bump-junit-to-v5
branch
from
463d3ce to
f498c33
Compare
* Remove Goorvy/Spock un-necessary build config * Remove un-used AppVeyor * Remove un-used Bintray from build
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kind of change
[ ] Bug fix
[x] New non-breaking feature
[ ] New breaking feature
[ ] Documentation update
[x] Build improvement
Description
What is the goal of this pull request?
Initially bump JUnit to latests v5. But also includes some cleanup of the build scripts that I detected:
How does it achieve that?
Bump dependencies and adapt tests code to the new JUnit APIs.
Are there any alternative ways to implement this?
No
Are there any implications of this pull request? Anything a user must know?
No
Issue
If this PR fixes an open issue, please add a line of the form:
Fixes #Issue
Release notes
Please add a corresponding entry to the file CHANGELOG.adoc