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.
This PR primarily focuses on reflecting the deprecation of JUnit 4 within the Spring Batch project.
Here's a breakdown of the changes:
Documentation Update (
testing.adoc
):Javadoc Updates in Test Listeners (
JobScopeTestExecutionListener.java
,StepScopeTestExecutionListener.java
):JobScopeTestExecutionListener
andStepScopeTestExecutionListener
has been modified.@RunWith(SpringJUnit4ClassRunner.class)
annotation, specific to JUnit 4, has been removed from these examples.@SpringJUnitConfig
annotation, which is typically used with JUnit 5, has been added to these examples.Javadoc and Example Removal in
SpringBatchTest.java
:@SpringBatchTest
with JUnit 4 has been removed.@SpringBatchTest
annotation, indicating that "JUnit4 is deprecated in Spring Batch 6.0.0 and will be removed in a future release."In essence, these changes remove JUnit 4 specific examples and guidance, update documentation to reflect its deprecation, and point towards JUnit 5 (Jupiter) as the recommended testing framework.