Closed
Description
The next version of Jakarta Batch is being discussed here. This discussion shows that the next version will require a substantial maintenance effort and even some showstoppers for Spring Batch (like the CDI requirement if agreed upon). Based on Michael's comment in that discussion:
The number of users consuming Spring Batch via the spec is too small to warrant the ongoing maintenance
burden. Add to that, we were never able to fully validate our implementation due to the transaction pieces
of the TCK being dependent upon the entire application server certification process (unable to run in an
SE environment).
We have decided to remove the JSR implementation in v5.