Compatibility certification request for Eclipse OpenMQ 6.3.0-RC1 for Jakarta Messaging 3.1 (of Jakarta EE 10)

[OndroMih]

• [x] Organization Name ("Organization") and, if applicable, URL: Eclipse Foundation
• [x] Product Name, Version and download URL (if applicable): Eclipse OpenMQ 6.3.0-RC1
• [x] Specification Name, Version and download URL: Jakarta Messaging 3.1
• [x] TCK Version, digital SHA-256 fingerprint and download URL: Jakarta Messaging TCK 3.1.0, SHA-256: 3ea9e4d9eb6c7ebd2f60f920c1e76ea2e2928540b0eee78120a18453d5851644
• [x] Public URL of TCK Results Summary: https://github.com/eclipse-ee4j/openmq/releases/download/6.3.0-RC1-RELEASE/tck-summary.txt
• [x] Any Additional Specification Certification Requirements: None
• [x] Java runtime used to run the implementation: OpenJDK 11.0.2+9
• [x] Summary of the information for the certification environment, operating system, cloud, ...:
  • TCK executed using the OpenMQ Jenkins instance, the 2_openmq-run-tck-against-staged-build job
• [x] By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.
• [x] By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

[OndroMih]

The TCK used wasn't the final version, putting this on hold until the final TCK is released and GlaasFish passes it.

[OndroMih]

Turned into a request for OpenMQ instead of GlassFish. The TCK used is a final one, no further modifications are planned, except possibly an update to the TCK guide that doesn't have any impact on certification.

Removing the On Hold status, all is ready for reviewing this certification request.

[pzygielo]

TCK executed using the OpenMQ Jenkins instance, the 2_openmq-run-tck-against-staged-build job

Perhaps it could be updated to refer to 39th build (for RC1) or to drop build number to have just the link to the job?

[OndroMih]

Updated to 39th build in Jenkins.

[pzygielo]

Please consider updating for TCK executed with promoted bundle:

• https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/promoted/eftl/jakarta-messaging-tck-3.1.0.zip, SHA256_TCK=3ea9e4d9eb6c7ebd2f60f920c1e76ea2e2928540b0eee78120a18453d5851644
• https://github.com/eclipse-ee4j/openmq/releases/download/6.3.0-RC1-RELEASE/tck-summary.40.txt
• https://ci.eclipse.org/openmq/job/2_openmq-run-tck-against-staged-build/40/

[dblevins]

@OndroMih Looks like as soon as we get a TCK run against the promoted TCK above we're good to go. Can you let me know if that's planned?

[OndroMih]

I've updated the info according to the build https://ci.eclipse.org/openmq/job/2_openmq-run-tck-against-staged-build/40/ as @pzygielo requested.