Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakartabatch-dev] Batch 2.1.0 Release Completed !

The Jakarta Batch 2.1 release review PR completed and so we are done !

 

(Some links for reference):

https://github.com/jakartaee/specifications/pull/438

https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/240

https://projects.eclipse.org/projects/ee4j.batch/releases/2.1.0

 

I released the API, TCK artifacts to Maven Central (for jbatch impl I’ll wait until the final release of the CDI dependency) and tagged the GH repos.

If there is anything else I forget re: “cleanup” or finalization feel free to let me know.

 

Thinking back at how to summarize the 2.1 contents, I’d describe it as:

 

  1. Move to Java 11 as part of EE 10 (though API language features probably still Java 6, FWIW)
  2. primitive wrapper types
    1. technically CDI + non-CDI
  3. CDI
    1. load as Bean first
    2. method/ctor parm ctx/prop injection
    3. batch thread context
    4. implications of CDI
      1. app scoped, artifact into artifact
    5. JobOperator bean should be provided, but app’s takes precedence
    6. (We didn’t call this out as a goal or explicitly test but I think an implication is that the step/job-scoped portable extensions of BatchEE & JBeret should now be well-defined in a Jakarta Batch  impl)
  4. Test automation - run TCK – Arquillian (only of use to the project, not end user app devs obviously)

 

Anything I missed?

 

Thanks again all who contributed, especially Ondro and Romain!

 

Scott Kurz


Back to the top