Skip to content

[junit] Use junit vintage instead of junit legacy fixes #2330#2483

Merged
hazendaz merged 3 commits intospotbugs:masterfrom
hazendaz:fix-junit
Jul 28, 2023
Merged

[junit] Use junit vintage instead of junit legacy fixes #2330#2483
hazendaz merged 3 commits intospotbugs:masterfrom
hazendaz:fix-junit

Conversation

@hazendaz
Copy link
Copy Markdown
Member

@hazendaz hazendaz commented Jul 22, 2023

behaves the same but stops directly using legacy parts so that we are firmly using modern api. Any junit 4 left then needs separately migrated to 5 as we should no longer support junit 4 in our builds. Fixes #2330


Make sure these boxes are checked before submitting your PR -- thank you!

  • [x ] Added an entry into CHANGELOG.md if you have changed SpotBugs code

hazendaz added 2 commits July 22, 2023 14:10
behaves the same but stops directly using legacy parts so that we are firmly using modern api.  Any junit 4 left then needs separately migrated to 5 as we should no longer support junit 4 in our builds.
@hazendaz hazendaz changed the title [junit] Use junit vintage instead of junit legacy [junit] Use junit vintage instead of junit legacy fixes #2330 Jul 22, 2023
@hazendaz hazendaz requested a review from JuditKnoll July 22, 2023 18:36
@hazendaz hazendaz self-assigned this Jul 22, 2023
@hazendaz
Copy link
Copy Markdown
Member Author

I did accidentally mark one at 5.9.0. However, renovate will fix and 5.10.0 is now out, so merging.

@hazendaz hazendaz merged commit 3d989c6 into spotbugs:master Jul 28, 2023
@hazendaz hazendaz deleted the fix-junit branch July 28, 2023 01:51
@hazendaz hazendaz added this to the SpotBugs 4.8.0 milestone Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mix of junit4 and junit5 on classpath confuses Eclipse

3 participants