MicroProfile 5.0 Compatible Certification Request - Payara Server Community (Web Profile) 6.2022.1.Alpha2

[Pandrex247]

• [x] Organization Name ("Organization") and, if applicable, URL:
  
  • Payara Services Ltd
• [x] Product Name, Version and download URL (if applicable):
  
  • Payara Server Community (Web Profile) 6.2022.1.Alpha2
• [x] Specification Name, Version and download URL:
  
  • MicroProfile 5.0
• [ ] (Optional) TCK Version, digital SHA-256 fingerprint and download URL:
  
• [x] Public URL of TCK Results Summary:
  
  • https://docs.payara.fish/community/docs/microprofile-certification/6.2022.1.Alpha2/microprofile-5.0-tck-results-web-6.2022.1.Alpha2.html
• [x] Any Additional Specification Certification Requirements:
  
  • The 11 skipped tests in MicroProfile Rest Client come from the ReactiveStreamsPublisherTest, which is an optional spec that Payara Server Community (Web Profile) 6.2022.1.Alpha2 does not support.
• [x] Java runtime used to run the implementation:
  
  • Zulu 11.54.25 (11.0.14.1)
• [x] Summary of the information for the certification environment, operating system, cloud, ...:
  
  • Linux, Ubuntu 20.04 LTS
• [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.

[smillidge]

Does anybody look at these or do we close through lazy consensus. Also how do we get listed as a Compatible Implementation?

[Emily-Jiang]

Does anybody look at these or do we close through lazy consensus. Also how do we get listed as a Compatible Implementation?

Obviously the lazy consensus kicks in if the issue was not accpeted/rejected with 14 days. I will bring this up to have a better process of reviewing the CCRs.

@smillidge here has instruction on how to get listed.

[smillidge]

@Emily-Jiang thanks for the pointer

btw there is no issue template "New Compatible Implementations To be Added" as described in the linked doc in the Marketing GitHub. I will get our team to raise "Compatible Implementations Announcement" as that seems to be the closest.