Certification Request for jbatch v2.1.0-M2 + jakarta batch api v2.1.0

[scottkurz]

• Organization Name ("Organization") and, if applicable, URL
  IBM - OpenLiberty - https://openliberty.io/

• Implementation Name, Version and download URL (if applicable)
  The former reference implementation, informally known as "jbatch", Version 2.1.0-M2, together with the Jakarta Batch API v2.1.0. For the "jbatch" implementation, we provide Maven download links for implementation and SPI jars. The project source repository is here. The Jakarta Batch API Maven coordinates are: jakarta.batch:jakarta.batch-api:2.1.0.

• Product Name, Version and download URL (if applicable)
  N/A - the implementation is tested outside of a "product".

• Specification Name, Version and download URL
  Jakarta Batch, Version 2.1. Download at: https://jakarta.ee/specifications/batch/2.1/

• TCK Version, digital SHA-256 fingerprint and download URL

• Jakarta Batch TCK Version 2.1.0 - official download URL will be: https://download.eclipse.org/jakartaee/batch/2.1/jakarta.batch.official.tck-2.1.0.zip
• This run captured against staged TCK location with download URL: https://download.eclipse.org/jakartabatch/tck/eftl/jakarta.batch.official.tck-2.1.0.zip

SHA-256 fingerprint
SHA256(jakarta.batch.official.tck/target/jakarta.batch.official.tck-2.1.0.zip)= cb0cb0d59be2e59ec66e9638be2b5c78da7d03a8cfe675409e8749010e483e5c

• Public URL of TCK Results Summary
  https://github.com/WASdev/standards.jsr352.jbatch/wiki/jbatch-v2.1.0-M2-tck-v2.1.0

• Any Additional Specification Certification Requirements
  N/A

• Java runtime used to run the implementation
  Java 11 and Java 17. Output of: java -version shown for

  Java 11

  openjdk version "11.0.14.1" 2022-02-08
  IBM Semeru Runtime Open Edition 11.0.14.1 (build 11.0.14.1+1)
  Eclipse OpenJ9 VM 11.0.14.1 (build openj9-0.30.1, JRE 11 Linux amd64-64-Bit Compressed References 20220210_379 (JIT enabled, AOT enabled)
  OpenJ9   - 9dccbe076
  OMR      - 56c3376ba
  JCL      - 5c423dacd0 based on jdk-11.0.14.1+1)
  

  Java 17

  openjdk version "17.0.2" 2022-01-18
  IBM Semeru Runtime Open Edition 17.0.2.0 (build 17.0.2+8)
  Eclipse OpenJ9 VM 17.0.2.0 (build openj9-0.30.0, JRE 17 Linux amd64-64-Bit Compressed References 20220128_115 (JIT enabled, AOT enabled)
  OpenJ9   - 9dccbe076
  OMR      - dac962a28
  JCL      - 64cd399ca28 based on jdk-17.0.2+8) 
  

• Summary of the information for the certification environment, operating system, cloud, ...

  • For Java 11 we have:

    + uname -a
    Linux 2f0d2cbee4fb 5.10.47-linuxkit #1 SMP Sat Jul 3 21:51:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
    + cat /etc/os-release
    NAME="CentOS Linux"
    VERSION="7 (Core)"
    ID="centos"
    ID_LIKE="rhel fedora"
    VERSION_ID="7"
    PRETTY_NAME="CentOS Linux 7 (Core)"
    ANSI_COLOR="0;31"
    CPE_NAME="cpe:/o:centos:centos:7"
    HOME_URL="https://www.centos.org/"
    BUG_REPORT_URL="https://bugs.centos.org/"
     
    CENTOS_MANTISBT_PROJECT="CentOS-7"
    CENTOS_MANTISBT_PROJECT_VERSION="7"
    REDHAT_SUPPORT_PRODUCT="centos"
    REDHAT_SUPPORT_PRODUCT_VERSION="7"
    

  • For Java 17, the /etc/os-release info is the same, but we have

    + uname -a
    Linux 461dee04a917 5.10.47-linuxkit #1 SMP Sat Jul 3 21:51:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
    

• By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.

• By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

[scottkurz]

In response to the v2.1.1 service release of Jakarta Batch TCK we re-ran the newer v2.1.1 TCK against jbatch (against v2.1.1 of the jbatch impl itself).

In this new run, all TCK tests passed.

This provides evidence that the changes made from v2.1.0 to v2.1.1 in response to the TCK challenges described in the link above did not affect the validity of this original certification request (which had been made running the original v2.1.0 TCK against an earlier version of the jbatch impl).

We included some more detailed results here:
https://github.com/WASdev/standards.jsr352.jbatch/wiki/jbatch-v2.1.1-tck-v2.1.1

[scottkurz]

In response to the v2.1.5 Jakarta Batch TCK update, we re-ran the newer v2.1.5 TCK against jbatch (against v2.1.1 of the jbatch impl itself).

In this new run, all TCK tests passed. Also the tests were run using Java 21 to exercise the new support for Java 21 in the v2.1.5 TCK.

This provides evidence that the changes made from v2.1.0 to v2.1.1 and v2.1.5 in response to TCK challenges did not affect the validity of this original certification request (which had been made running the original v2.1.0 TCK against an earlier version of the jbatch impl).

We included some more detailed results here:
https://github.com/WASdev/standards.jsr352.jbatch/wiki/jbatch-v2.1.1-tck-v2.1.5