Home

Jakarta Batch wiki

Mission statement:

• Release Batch 2.0 Api/Spec/TCK as part of EE 9

• Leverage interest in EE 9 to build momentum for an update with new Batch function (e.g. v2.1)

EE 9 Plan

https://github.com/eclipse-ee4j/batch-api/issues/7

OFFICIAL ISSUES

The ONLY official issues are here:

1. API https://github.com/eclipse-ee4j/batch-api

2. TCK https://github.com/eclipse-ee4j/batch-tck/

The implication here is that previously-opened issues on the former JSR 352 issue tracker from the former JCP-based project, are NOT, at least for now, going to be automatically opened/re-opened on the new issue tracker backlog.

At the same time, we try to transparently link to the old issues and discussions where available. See page. We expect to discuss this more on the Jakarta Batch mailing list soon.

Ideas for Next Steps

At this point the project has not collectively prioritized anything, so these are just ideas

Organization

• labels of api/tck

• Reading through legacy issues to decide which ones to reopen

TCK

• convert to Arquillian?

Other Ideas

• Build/release - Set up real CI pipeline, (either the manual

• Website, e.g. the official EE4J Eclipse project page [here](https://projects.eclipse.org/projects/ee4j.batch) and/or adding a github.io GitHub Pages site

Discussions We Need to Have

• Longer-term: what batch impl to use in Glassfish?

• Back compatibility when expanding TCK, especially for function defined in 1.0 (which should have been tested).

Links:

• Project Home

• Original Jakarta Batch proposal

TCK Results:

• Link to TCK Results.