Legacy Issues

Issues opened earlier, e.g. the previous JSR 352 incarnation of the project.

These will not be considered part of the official issue backlog for Jakarta Batch unless/until someone takes the step of opening up a new issue in the new projects: https://github.com/eclipse-ee4j/batch-api and https://github.com/eclipse-ee4j/batch-tck.

1. Issues from https://github.com/WASdev/standards.jsr352.batch-spec/issues
   • spec doc, API
2. JSR 352 bugzilla issues from https://github.com/WASdev/standards.jsr352.batch-spec
   • See CSV and XML files at: https://github.com/WASdev/standards.jsr352.batch-spec/tree/master/java.net.backup
3. https://github.com/WASdev/standards.jsr352.tck/issues
   • coverage gaps - What are rules for expanding coverage of already settled function?
   • automation infrastructure, doc/spec linkage, typos/cleanup, logic bugs (not related to spec coverage)
4. JBatch RI issues: https://github.com/WASdev/standards.jsr352.jbatch/issues
   • most are impl issues (not relevant to spec), scrub for spec issues
5. Issues accumulated by individual implementations
   • e.g. Open Liberty: https://github.com/OpenLiberty/open-liberty/issues/10102