Review: CCR for Azul Payara 6.38.0 — Jakarta EE Platform 10.0

[Copilot]

Review of the compatibility certification request for Azul Payara 6.38.0 against Jakarta EE Platform 10.0, following the CCR Review Guidance. This is a review-only task; no repository files change.

Verified

• Attestations: both required checkboxes (EFTL, TCK requirements) checked.
• Platform TCK: jakarta-jakartaeetck-10.0.0.zip on the official download.eclipse.org base URL; SHA-256 matches published .sha256 (7874244f…08215a5e).
• Required TCK set: all 15 standalone TCKs for Platform 10 full profile present (Activation, Authentication, Batch, Bean Validation, Concurrency, CDI, Debugging Support, Dependency Injection, JSON Binding, JSON Processing, Faces, Mail, RESTful WS, Security, XML Binding).
• Dependent hashes: all 15 SHA-256 values verified against the official <tck>.zip.sha256 on download.eclipse.org.
• Runtime: Zulu/OpenJDK 11.0.19 — supported for Jakarta EE 10.

Minor issues (hashes correct, filenames mislabeled)

• Activation: CCR file activation-tck-2.1.2.zip; official artifact is jakarta-activation-tck-2.1.2.zip (hash matches official).
• XML Binding: heading says 4.0.1 but filename says …-4.0.0.zip; provided hash 146be8dc… matches official 4.0.1 (official 4.0.0 hash differs), so the correct 4.0.1 TCK was used — filename should read 4.0.1.

Needs manual reviewer check (domains blocked in sandbox)

• TCK Results Summary (docs.payara.fish): confirm no login, product-associated/permanent, mirrors CCR detail, all tests pass with no failures.
• Product download (nexus.dev.payara.fish, enterprise evaluation repo): confirm version/accessibility.
• Spec page jakarta.ee/specifications/platform/10.

Recommendation

Hashes and required TCK set check out against the Eclipse download center. Pending manual confirmation of the all-pass Results Summary and the evaluation download URL; suggest the filer correct the two filenames noted above.

[ivargrimstad]

See PR text and issue comment

[Copilot]

See PR text and issue comment

Review complete. Summary:

• Platform TCK jakarta-jakartaeetck-10.0.0.zip — official base URL, SHA-256 matches published .sha256 (7874244f…).
• All 15 required standalone TCKs for Platform 10 full profile are present, and every SHA-256 was verified against the official <tck>.zip.sha256 on download.eclipse.org.
• Two cosmetic filename issues only (hashes are correct): Activation listed as activation-tck-2.1.2.zip vs official jakarta-activation-tck-2.1.2.zip; XML Binding filename says …-4.0.0.zip while the hash 146be8dc… is the official 4.0.1 artifact.

Items that require your manual check (domains blocked in this sandbox): the TCK Results Summary page on docs.payara.fish (no login, permanent/product-associated, all tests pass with no failures), the nexus.dev.payara.fish evaluation download URL, and jakarta.ee/specifications/platform/10. Everything verifiable from the Eclipse download center checks out.

[ivargrimstad]

@copilot re-verify

[Copilot]

@copilot re-verify

Re-verified. All 16 SHA-256 values still match the official published <tck>.zip.sha256 on download.eclipse.org:

• Platform TCK jakarta-jakartaeetck-10.0.0.zip — 7874244f…08215a5e ✔
• All 15 dependent standalone TCKs (Activation, Authentication, Batch, Bean Validation, Concurrency, CDI, Debugging, Dependency Injection, JSON Binding, JSON Processing, Faces, Mail, RESTful WS, Security, XML Binding) ✔

The two prior filename notes remain cosmetic only (hashes correct): Activation official file is jakarta-activation-tck-2.1.2.zip; XML Binding hash 146be8dc… is the official 4.0.1 artifact though the CCR filename reads …-4.0.0.zip.

Still not reachable from this sandbox (DNS blocked), so these need your manual confirmation: the docs.payara.fish TCK Results Summary (no login, permanent, all tests pass), the nexus.dev.payara.fish evaluation download, and jakarta.ee/specifications/platform/10. Everything verifiable against the Eclipse download center checks out.