Certification Request for jbatch v1.0.3 + jakarta batch api v1.0.2

[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 1.0.3, together with the Jakarta Batch API v1.0.2. 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:1.0.2.

• 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 1.0.

• TCK Version, digital SHA-256 fingerprint and download URL
  Jakarta Batch TCK Version 1.0.2 - (will be) available for official download at URL: https://download.eclipse.org/jakartaee/batch/1.0/eclipse-batch-tck-1.0.2.zip.

Provisional results were obtained via running against staged zip here. TODO: We need to come back and adjust SHA256 for the final binary.
(Staged zip) SHA256: 26855ba168b814f65af1251cc853dc6455d2f9ecd2b215f06327ec090b32542a

• Public URL of TCK Results Summary
  https://github.com/WASdev/standards.jsr352.jbatch/wiki/jbatch-v1.0.3-tck-v.1.0.2

• Any Additional Specification Certification Requirements
  N/A

• Java runtime used to run the implementation
  Java 8

  $ java -version 
  openjdk version "1.8.0_212"
  OpenJDK Runtime Environment (build 1.8.0_212-b04)
  OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
  

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

  $ uname -a
  Linux skr 3.10.0-957.21.3.el7.x86_64 #1 SMP Fri Jun 14 02:54:29 EDT 2019 x86_64 x86_64 x86_64 GNU/Linux
  
  $ cat /etc/os-release
  NAME="Red Hat Enterprise Linux Server"
  VERSION="7.6 (Maipo)"
  

• 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.

[kwsutter]

Accepted.

[scottkurz]

Looking back on this, there a couple "TODO" comments. I just want to clarify this is not incomplete or missing some rigor.

There's a "chicken and egg" problem in that the certification of the compatible impl is needed to finalize the specification... but at the time the first certification request issue (e.g. this issue) is being written up, the specification is not yet finalized.

So I'll leave the original comment above alone, but add a couple clarifications:

1. Where it says above:

Jakarta Batch TCK Version 1.0.2 - (will be) available for official download at URL: https://download.eclipse.org/jakartaee/batch/1.0/eclipse-batch-tck-1.0.2.zip.
This URL is now: https://download.eclipse.org/jakartaee/batch/1.0/jakarta.batch.official.tck-1.0.2.zip

2. Where it says:

Provisional results were obtained via running against staged zip here. TODO: We need to come back and adjust SHA256 for the final binary.
(Staged zip) SHA256: 26855ba168b814f65af1251cc853dc6455d2f9ecd2b215f06327ec090b32542a

This does indeed match the hash of the final TCK, as you can see if you download this: https://download.eclipse.org/jakartaee/batch/1.0/jakarta.batch.official.tck-1.0.2.zip.sha256