Compatibility Certification Request for Eclipse Jersey 3.1.0-M3

[jansupol]

• [x] Organization Name ("Organization") and, if applicable, URL\ Eclipse Foundation
• [x] Product Name, Version and download URL (if applicable)\ Eclipse Jersey 3.1.0-M3, see TCK Result Summary for the download links
• [x] Specification Name, Version and download URL\ Jakarta RESTful Web Services 3.1
• [x] TCK Version, digital SHA-256 fingerprint and download URL Jakarta RESTful Web Services TCK 3.1.0, SHA-256: ea8cd6cc857af55f19468bbb09e8a30f41c60e8f7413a093e7007c3902a49070
• [x] Public URL of TCK Results Summary\ TCK results summary
• [x] Any Additional Specification Certification Requirements\ None
• [x] Java runtime used to run the implementation\ JDK 11.0.2+9
• [x] Summary of the information for the certification environment, operating system, cloud, ...\ Linux
• [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.

[spericas]

Approved

[mkarg]

@spericas Are there any rules what the committers need to do for such an approval? I assume the EF wants us to perform specific tasks, right? So it might make sense to push a checklist with those tasks into this issue.