Skip to content

Conversation

@marcphilipp
Copy link
Member

@marcphilipp marcphilipp commented Oct 10, 2025

Whether the Vintage engine should report discovery issues such as
deprecation notices is now configurable via the new
junit.vintage.discovery.issue.reporting.enabled configuration
parameter.

Resolves #5030.


Definition of Done

Whether the Vintage engine should report discovery issues such as
deprecation notices is now configurable via the new
`junit.vintage.discovery.issue.reporting.enabled` configuration
parameter.

Resolves #5030.
Copy link
Member

@sormuras sormuras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor nit, otherwise looks good.

Co-authored-by: Christian Stein <[email protected]>
@marcphilipp marcphilipp merged commit 4041234 into main Oct 12, 2025
16 checks passed
@marcphilipp marcphilipp deleted the marc/5030-allow-disabling-vintage-discovery-issues branch October 12, 2025 12:30
marcphilipp added a commit that referenced this pull request Oct 12, 2025
Whether the Vintage engine should report discovery issues such as
deprecation notices is now configurable via the new
`junit.vintage.discovery.issue.reporting.enabled` configuration
parameter.

Resolves #5030.

(cherry picked from commit 4041234)
matriv added a commit to crate/crate that referenced this pull request Oct 21, 2025
Currently the upgrade leads to spam messages like the following:
```
The JUnit Vintage engine is deprecated and should only be used temporarily
while migrating tests to JUnit Jupiter or another testing framework with
native JUnit Platform support
```

The issue is addressed with: junit-team/junit-framework#5049
but will be released with 6.0.1.

Follows: #18542
mergify bot pushed a commit to crate/crate that referenced this pull request Oct 21, 2025
Currently the upgrade leads to spam messages like the following:
```
The JUnit Vintage engine is deprecated and should only be used temporarily
while migrating tests to JUnit Jupiter or another testing framework with
native JUnit Platform support
```

The issue is addressed with: junit-team/junit-framework#5049
but will be released with 6.0.1.

Follows: #18542
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide a way to opt out of JUnit Vintage engine deprecation

4 participants