| [jakartabatch-dev] Generics need to move post-EE9 |
So while I raised the issue:
https://github.com/eclipse-ee4j/batch-api/issues/13
asking should we consider adding generics (for the various "item" types and others), I think it is simply too late at this point.
I think there was an opportunity and unfortunately I just wasn't engaged enough in the project to take advantage of this. At this point we'd be jeopardizing the whole EE 9 plan.
This would be the case even if we knew exactly what changes we wanted to make and had tested them in runtime impls, which isn't the case.
Looking ahead,
I'm not sure of an easy, non-breaking way to make such a change. If we were to follow semantic version that could even push generics into a 3.0 release.
Not quite the normal progression to go so long between 1.0 and 2.0, then quick do a 3.0.
The generics seem even more useful with jobs constructed in Java (rather than XML)... maybe if we tie generics to that function, which we've also talked about recently, we would have a decent-enough story.
Thoughts?
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------