-
Notifications
You must be signed in to change notification settings - Fork 78
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
Spring Boot 3.2 Migration breaks Testcontainers due to exclusion of JUnit 4 as part of JUnit4to5Migration #477
Comments
Hi @tedyoung ; Thanks for chiming in with those details! For now I've applied the same fix as we saw earlier in #430 There's a bit of a balance here where that exclusion often helps to fully wean folks off JUnit 4; but of course for Testcontainers we can't yet fully do that. Luckily the folks at AtomicJar/Docker are also involved here (see our Testcontainers recipes), so who knows we might be able to migrate their users off of JUnit 4 with recipes in the future. |
Thanks for the quick response! I hope that the Testcontainer folks fix testcontainers/testcontainers-java#970 before it hits its 6th birthday. 😦 |
You're welcome; glad this was an easy fix. We just did a release yesterday, but until the next one in a week or two you can use |
What version of OpenRewrite are you using?
Ran command via
mvn -U org.openrewrite.maven:rewrite-maven-plugin:run -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-spring:RELEASE -Drewrite.activeRecipes=org.openrewrite.java.spring.boot3.UpgradeSpringBoot_3_2
Which used Rewrite 5.22.0, relevant output:
What is the smallest, simplest way to reproduce the problem?
This Spring Boot project's pom.xml:
What did you expect to see?
I expected only the Spring Boot parent version to change, with no other changes:
What did you see instead?
As in issue #429, the JUnit 4 exclusion was added to the Testcontainers dependency block, which breaks the functionality of Testcontainers:
The text was updated successfully, but these errors were encountered: