[backport] Add support for JUnit 'vintage' attribute on classpath#3910
Merged
laeubi merged 1 commit intoeclipse-tycho:tycho-4.0.xfrom Jun 1, 2024
Merged
[backport] Add support for JUnit 'vintage' attribute on classpath#3910laeubi merged 1 commit intoeclipse-tycho:tycho-4.0.xfrom
laeubi merged 1 commit intoeclipse-tycho:tycho-4.0.xfrom
Conversation
JDT supports a new classpath attribute on the JUnit5 container that disables the vintage engine. This is especially important if one wants to write plain JUnit5 test as it is otherwise easy to mix up Junit4/5. This now adds a testcase that shows that such mixed usage would fail compilation. (cherry picked from commit 13489c6)
Test Results 591 files 591 suites 3h 54m 9s ⏱️ Results for commit 45bca23. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
JDT supports a new classpath attribute on the JUnit5 container that disables the vintage engine. This is especially important if one wants to write plain JUnit5 test as it is otherwise easy to mix up Junit4/5.
This now adds a testcase that shows that such mixed usage would fail compilation.
(cherry picked from commit 13489c6)