Compatibility certification request for EE4J implementation of Jakarta Standard Tag Library 3.0

[arjantijms]

• [x] Organization Name ("Organization") and, if applicable, URL Eclipse Foundation
• [x] Product Name, Version and download URL (if applicable) Eclipse EE4J implementation of Jakarta Standard Tag Library 3.0.0 Eclipse GlassFish 7.0.0-M4
• [x] Specification Name, Version and download URL Jakarta Standard Tag Library 3.0
• [x] TCK Version, digital SHA-256 fingerprint and download URL Jakarta Standard Tag Library 3.0.0, SHA-256: 996c9abc6561134cea986107da0648c2a33277d2f765475994ff9b16da70cb5a
• [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 OpenJDK 11.0.2, 17.0.1, 18-ea
• [x] Summary of the information for the certification environment, operating system, cloud, ... Debian GNU/Linux 10
• [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.

[volosied]

@arjantijms Who should approve this compatibility request (item 4 of https://github.com/eclipse-ee4j/jstl-api/issues/230) ?

I also verified the sha256 hashes match the site:

openssl sha256 jakarta-tags-tck-3.0.0.zip 
SHA256(jakarta-tags-tck-3.0.0.zip)= 996c9abc6561134cea986107da0648c2a33277d2f765475994ff9b16da70cb5a 

Edit: I also wanted to ask you about this checklist item:

The compatible implementation project/vendor MUST send an email to [tck@eclipse.org](mailto:tck@eclipse.org) for approval of the compatible implementation for trademark usage.

Who should send this email? Glassfish?

Thank you

[arjantijms]

@volosied I think it's best if @pnicolucci would assert the CCR is complete. I can send the email, I'll cc you and @pnicolucci.

[pnicolucci]

@arjantijms @volosied this looks good to me! Here is my +1.

[pnicolucci]

Approved and closing.