[Copilot]

Review of the compatibility certification request for Azul Payara (Web Profile) 7.0.0 against the CCR Review Guidance. This is a review task — no repository files change.

Verification method: downloaded each referenced TCK and compared SHA-256 against the official .sha256 sidecars on download.eclipse.org, and cross-checked the required TCK set against the accepted EE 11 Web Profile CCRs #1290 and #1291.

Recommendation: not ready for approval — filer corrections required.

Passed

• Both attestation checkboxes checked.
• Main Platform TCK 11.0.1 link + base URL valid; SHA-256 matches official (b2c0ad6d…).
• 12 of 16 dependent TCK hashes match official values.

Must be fixed

• Spec named "Platform" not "Web Profile" — should reference Jakarta EE Web Profile 11 (jakarta.ee/specifications/webprofile/11).
• Broken link (404) — Annotations: jakarta-annotation-tck-3.0.0.zip (singular) → correct is jakarta-annotations-tck-3.0.0.zip (plural).
• Broken link (404) — CDI: …/ee4j/cdi/4.0/cdi-tck-4.1.0-dist.zip → 4.1.0 lives under …/cdi/4.1/.
• SHA-256 mismatches (CCR → official):
  • Annotations 3.0.0 8b916f1b… → 9421c6ca…
  • Authentication 3.1.0 9421c6ca… → 6ab2e521…
  • Concurrency 3.1.1 22728d72… → b064e189…
  • CDI 4.1.0 566c547e… → 446029ee…
• Missing required TCKs: Jakarta Data 1.0.x and Jakarta Debugging Support for Other Languages 2.0.0 (both present in Compatibility certification request for Open Liberty for Jakarta EE 11, Web Profile #1290/Compatibility certification request for IBM WebSphere Liberty for Jakarta EE 11, Web Profile #1291).

To confirm

• Jakarta Tags 3.0.1 is listed but absent from the accepted reference set.
• Older point releases vs. references (main TCK 11.0.1 vs 11.0.2; Authentication 3.1.0/3.1.1; EL 6.0.0/6.0.1; Faces 4.1.1/4.1.2; RESTful 4.0.0/4.0.1; Servlet 6.1.0/6.1.1).
• TCK Results Summary (docs.payara.fish) and product URL (nexus.dev.payara.fish evaluation repo) were unreachable from the review environment — a human should confirm the results page loads without login and reports all tests passing, and that the product download is publicly accessible.

[ivargrimstad]

See PR text

[Copilot]

See PR text

I re-verified against issue #1329 as updated on 2026-07-01. Since my initial review, the filer changed only the TCK Results Summary URL (now docs.azul.com) and corrected the product download URL. None of the "Must be fixed" items have been addressed in the issue body:

• Spec still named "Jakarta EE Platform 11.0" (specifications/platform/11) rather than Web Profile.
• Annotations link still jakarta-annotation-tck-3.0.0.zip (singular, 404) and SHA still 8b916f1b… (official 9421c6ca…).
• CDI link still …/ee4j/cdi/4.0/cdi-tck-4.1.0-dist.zip (404) and SHA still 566c547e… (official 446029ee…).
• Authentication SHA still 9421c6ca… (official 6ab2e521…); Concurrency SHA still 22728d72… (official b064e189…).
• Jakarta Data 1.0.x and Jakarta Debugging Support 2.0.0 still absent.

So the recommendation stands: not ready for approval. The updated docs.azul.com results page and nexus.dev.payara.fish product download are not resolvable from the review sandbox, so those two still need human confirmation.

If a specific change to the PR text is wanted beyond this re-verification, could you point to it? The PR has no file diff by design (CCR review task).

[ivargrimstad]

@copilot re-verify

[Copilot]

@copilot re-verify

Re-verified against the current issue #1329 — all previously flagged "Must be fixed" items are now resolved:

• ✅ Spec now Jakarta EE Web Profile 11.0 (specifications/webprofile/11/).
• ✅ Annotations link corrected to jakarta-annotations-tck-3.0.0.zip (200); SHA now 9421c6ca… (matches official sidecar).
• ✅ CDI link corrected to …/ee4j/cdi/4.1/cdi-tck-4.1.0-dist.zip (200); SHA now 446029ee… (confirmed by download+hash).
• ✅ Authentication SHA now 6ab2e521…; Concurrency SHA now b064e189… (both match official sidecars).
• ✅ Jakarta Data 1.0.1 (92babb60…) and Jakarta Debugging Support 2.0.0 (71999815…) added; links resolve and SHAs match official sidecars.

The 12 originally-passing hashes remain valid, and the main Platform TCK 11.0.1 SHA (b2c0ad6d…) is unchanged and correct. Everything I can verify now checks out.

Note: docs.azul.com (results summary) and nexus.dev.payara.fish (product download) remain unresolvable from the review sandbox, so those two still rely on human confirmation. Jakarta Tags 3.0.1 is still listed (not in #1290/#1291) but an extra TCK is harmless; main TCK 11.0.1 is an older point release than the 11.0.2 used in #1290/#1291 but is a valid official release with a matching SHA.