Adding CompositeItemProcessor use case test#1
Open
hoserdude wants to merge 1 commit intogalak75:masterfrom
hoserdude:master
Open
Adding CompositeItemProcessor use case test#1hoserdude wants to merge 1 commit intogalak75:masterfrom hoserdude:master
hoserdude wants to merge 1 commit intogalak75:masterfrom
hoserdude:master
Conversation
+ gitignore, + latest milestone of batch 3.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The CompositeItemProcessor use case was failing to wire up the @BeforeStep even in the Singleton scope, so I tagged along with your simple use case to demonstrate it failing in a simple test.