Skip to content
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

JUnit Jupiter's vintage engine was removed in Spring Boot 2.4 #192

Closed
josemariavillar opened this issue Jan 25, 2022 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@josemariavillar
Copy link

Good morning,

The recipe that upgrades to Spring Boot 2.4 includes by default the migration from JUnit4 to 5. This recipe is responsible for excluding the junit-vintage-engine dependency since the JUnit Jupiter's vintage engine was removed in Spring Boot 2.4. But if for some reason the application has this dependency defined in its POM it is not removed, having to remove it manually for it to work. wouldn't it be logical to include that this dependency is removed if it is defined?

https://github.com/openrewrite/rewrite-spring/blob/ee19bc944fc141da4de3effc07313076a638e0ab/src/main/resources/META-INF/rewrite/spring-boot2-upgrade-version.yml#L155

@pway99 pway99 added the bug Something isn't working label Jan 26, 2022
@pway99
Copy link
Contributor

pway99 commented Jan 26, 2022

thanks @josemariavillar, lots of effort on rewrite maven resolution and recipes going on right now. Once those changes are complete we can revisit this issue and make any necessary changes.

@pway99 pway99 self-assigned this Feb 18, 2022
@pway99 pway99 assigned pway99 and unassigned pway99 Mar 10, 2022
@pway99 pway99 transferred this issue from openrewrite/rewrite-spring Mar 17, 2022
@pway99 pway99 closed this as completed in 0f14178 Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants