GH-4544 Openrewrite migration to junit5. #4851
Draft
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.
Junit4 is still used in a few places, one for lucene or guavatestlibs that don't have an junit4 equivalent
GitHub issue resolved: #4544
Briefly describe the changes proposed in this PR:
mvn -U org.openrewrite.maven:rewrite-maven-plugin:run \ -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-testing-frameworks:RELEASE \ -Drewrite.activeRecipes=org.openrewrite.java.testing.junit5.JUnit4to5Migration
Then reverting any module with compiler issues and throwing away all pom changes.
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resources
to format from the command line)