Releases: WASdev/standards.jsr352.jbatch
2.1.1
2.1.0
2.0.0
2.0.0-M7
jbatch 2.0.0-M5
Significant change since the job XML XSD has changed, and therefore previous job XMLs are no longer valid (and impls are required to validate before executing jobs). There is no ability for the impl to execute older job definitions, either previous iterations of the 2.0 schema or the 1.0 (original JSR 352 schema), at this version.
jbatch 2.0.0-M3
- Fixed incorrect package prefix (wrongly had been converted to jakarta.*):
#64
jbatch 2.0.0-M2
M2 release, major changes includes:
- Update OSGi bundle manifests to remove javax versions and avoid hyphenated versions.
jbatch 2.0.0-M1
M1 release using jakarta.* packages for Jakarta EE 9. Depends on other milestone/alpha dependencies.
impl-1.0.3
scottkurz
Scott Kurz
Maven version 1.0.3 of the com.ibm.jbatch.container, com.ibm.jbatch.spi modules.
Fixes issues:
Note: As noted in the 1.0.2 update, we are no longer updating the API version modules at the same time. This might lead one to think that there has been a change in the com.ibm.jbatch.spi module, given that it's now been updated. In fact there is no change from 1.0.2 to 1.0.3 in com.ibm.jbatch.spi and we simply did not bother refactoring the build process in a way to allow us to update the com.ibm.jbatch.container module separately.
Maven version 1.0.2 of the com.ibm.jbatch.container, com.ibm.jbatch.spi modules
scottkurz
Scott Kurz
Maven version 1.0.2 of the com.ibm.jbatch.container, com.ibm.jbatch.spi modules.
Fixes issues:
- Glassfish 5 Weld (CDI) level breaks batch app deployment #53
- For partitioned steps, allow-start-if-complete=true does not result in re-running the partitions #36
- Set SCHEMA is not valid SQL in MySQL #11
Note: This may not be a complete list. There may have been issues from the java.net bugzilla that were fixed that aren't mentioned here.
Note: We've been inconsistent on whether we should update all three modules with similar versions at the same time: (e.g. 1.0.2), or if we should only update the version for a particular module if something has changed. Since in this last release we've done the latter (and not updated the javax.batch version), we will feel free to continue having the module versions differ going forwards.