This is an automated email from the ASF dual-hosted git repository.

jungm pushed a commit to branch ee11
in repository https://gitbox.apache.org/repos/asf/tomee-tck.git

commit 512aa8c19f35fff8ad86b2b9605cb2e4e1cae855
Merge: b8edfbe 848420b
Author: Markus Jung <[email protected]>
AuthorDate: Sun Jul 19 10:55:01 2026 +0200

    Merge branch 'ee11' into claude/tck-module-setup-check-0c52f9
    
    # Conflicts:
    #       KNOWN_ISSUES.md

 KNOWN_ISSUES.md                                    |  37 +-
 runner-standalone/README.md                        |  10 +-
 runner-standalone/exclusions/README.md             |   6 +-
 runner-standalone/exclusions/security-old.txt      |  18 +
 runner-standalone/pom.xml                          |   1 +
 runner-standalone/run-standalone-suite.sh          |   6 +-
 runner-standalone/security-old/pom.xml             | 488 +++++++++++++++++++++
 .../security-old/src/test/resources/tomee.xml      |  15 +
 8 files changed, 560 insertions(+), 21 deletions(-)

diff --cc KNOWN_ISSUES.md
index 19d7236,2f120fe..257c732
--- a/KNOWN_ISSUES.md
+++ b/KNOWN_ISSUES.md
@@@ -38,9 -38,10 +38,10 @@@ Detail lives next to each runner
  | jsonb | 295 tests, 1 F + 1 E | 2 tests | 2 Johnzon 2.1.0 gaps |
  | debugging | passes (4 SMAPs validated) | — | — |
  | security | 132 tests, 5 F + 2 E; signature test passes | 7 tests | TomEE 
Jakarta Security |
+ | security-old (JavaTest) | 83 tests, 82 pass, 1 F | 1 test | TomEE 
`SecurityContext.hasAccessToWebResource()` returns false for an authorized 
caller |
  | authentication | 106 tests, 1 F; signature test passes | 1 method (spi 
`CheckMsgInfoKey`) | TCK challenge #219 (hard-codes a JACC requirement) |
  | websocket | 737 tests, 3 E | 3 methods | Client container advertises 
permessage-deflate in the negotiated extension lists |
 -| faces (modern modules) | 327 tests, 45 F + 6 E (failsafe reruns inflate the 
counts; 10 distinct failing classes) | 10 classes | 1 TomEE faces-config gap + 
Mojarra/TomEE CDI-injection, whole-bean/method validation, and one Chrome ajax 
quirk |
 +| faces (modern modules + old-tck-selenium) | 298 tests, 0 F + 0 E, 17 
skipped (with exclusions applied) | 10 classes | 1 TomEE faces-config gap + 
Mojarra/TomEE CDI-injection, whole-bean/method validation, and one Chrome ajax 
quirk |
  | faces-old (JavaTest) | 5,391 tests, all pass (recorded run: 5 F from a 
foreign server answering :8080 mid-run; pass on re-run) | — | — (standalone 
mode, no exclusions) |
  | faces-signaturetest | passes against Plume's Mojarra 
(org.glassfish:jakarta.faces 4.1.9) | — | — |
  
@@@ -248,10 -259,18 +259,14 @@@ Need triage/fixes in the upstream proje
  Not product bugs — gaps in this repository's coverage.
  
  - **Modern faces reactor not in CI**: the `faces` runner (modern Arquillian
 -  modules plus the signature test) runs locally via
 -  `run-standalone-suite.sh`; it joins the Jenkins branch list once its
 -  baseline and exclusion wiring have a verified green run. The `faces-old`
 -  JavaTest half runs in CI.
 -- **Faces `old-tck-selenium` module uncovered**: the extracted TCK reactor
 -  ships an `old-tck-selenium` module (22 tests) that neither the `faces`
 -  runner (which drives faces22/23/40/41 + faces-signaturetest) nor the
 -  `faces-old` JavaTest runner executes; wire it into one of them.
 +  modules, the Chrome/Selenium `old-tck-selenium` modules, and the signature
 +  test) runs locally via `run-standalone-suite.sh`; it joins the Jenkins
 +  branch list once its baseline and exclusion wiring have a verified green
 +  run. The `faces-old` JavaTest half runs in CI.
+ - **Security `security-old` not in CI**: the `security-old` runner (the
+   reactor's legacy JavaTest `com.sun.ts.tests.securityapi` suite) runs
+   locally via `run-standalone-suite.sh` and is green with the reviewed
+   exclusion; it joins the Jenkins branch list once its baseline has settled.
  
  ## What CI runs
  
diff --cc runner-standalone/README.md
index 13017d0,243b163..b920ec9
--- a/runner-standalone/README.md
+++ b/runner-standalone/README.md
@@@ -59,9 -60,10 +60,10 @@@ derived from; with the default exclusio
  | Pages 4.0 | EFTL zip (installed as `jakarta.tck:jakarta-pages-tck:4.0.0`) | 
`pages` | **Passes 682/682 (0 failures, 0 errors, signature test included, no 
exclusions)** (2026-07-18). Needs the Central 
`jakarta.tck:common`/`signaturetest` support line at 11.1.1 with sigtest 2.6 
(the TCK pom's own pins depend on the unpublished JavaTest harness), and the 
overlay removes TomEE's global UTF-8 default encodings from conf/web.xml 
because the TCK asserts the spec default ISO-8859-1. Its TomEE [...]
  | Validation 3.1 | EFTL zip (installed as 
`jakarta.validation:validation-tck-tests:3.1.1`) | `validation` | **Runs: 1,049 
tests, 0 failures, no exclusions; the mandatory API signature test runs and 
passes** against the `jakarta.validation` packages the Plume distribution 
ships. Needs AssertJ 3.7.0 pinned (the published TCK jar is compiled against 
its covariant signatures) and the JAXB RI pinned as 
`jakarta.xml.bind.JAXBContextFactory` in the server JVM (Plume ships both MOXy 
and the RI; [...]
  | WebSocket 2.2 | EFTL zip (installed as 
`jakarta.tck:websocket-tck-spec-tests:2.2.0`) | `websocket` | **Runs: 737 
tests, 0 failures, 3 errors** (2026-07-18) against Tomcat's WebSocket 
implementation, driven through the `tomcat-websocket` client container; the 
signature test passes. The negative-deployment classes run and pass: an invalid 
server endpoint aborts the whole webapp deployment as the spec requires, and 
the runner's Arquillian extension (`NegativeDeploymentToleranceObserver`) [...]
- | Security 4.0 | Source reactor zip 4.0.1 | `security` (Maven module) | 
**Runs: 26 app modules plus the signature test, 132 tests, 5 failures, 2 errors 
at baseline; green with the reviewed exclusions (all 27 invoker projects pass, 
verified end-to-end 2026-07-18)**. The runner downloads and patches the 
reactor, injects a tomee-remote profile (including the 
`trustStore.path`/`trustStore.password` properties the OpenID modules' keytool 
steps read), and drives every module through the Maven [...]
+ | Security 4.0 | Source reactor zip 4.0.1 | `security` (Maven module) | 
**Runs: 26 app modules plus the signature test, 132 tests, 5 failures, 2 errors 
at baseline; green with the reviewed exclusions (all 27 invoker projects pass, 
verified end-to-end 2026-07-18)**. The runner downloads and patches the 
reactor, injects a tomee-remote profile (including the 
`trustStore.path`/`trustStore.password` properties the OpenID modules' keytool 
steps read), and drives every module through the Maven [...]
+ | Security 4.0 (legacy old-tck) | Source reactor zip 4.0.1 (old-tck built 
from bundled sources) | `security-old` (Maven module) | **Baseline 83 tests, 82 
pass, 1 failure (Plume, JDK 21, 2026-07-19); green with the reviewed 
exclusion.** The legacy JavaTest half exercises ~65 
`com.sun.ts.tests.securityapi` Client classes across the idstore (in-war, 
database, LDAP), ham (HTTP authentication mechanism) and securitycontext trees. 
It deploys through the TCK's own `tomcat` handler (WAR copy in [...]
  | Authentication 3.1 | Source reactor zip 3.1.2 | `authentication` (Maven 
module) | **Runs: 12 Web Profile modules plus the signature test; green with 
the reviewed exclusions (all 13 invoker projects pass, 0 failures, verified 
end-to-end 2026-07-18)**. The spi module registers the TCK's test 
`AuthConfigProvider` under Tomcat's JASPIC app-context naming 
(`Catalina/localhost /spitests_servlet_web`), so `ServletProfileSPITest` runs 
against Tomcat's `AuthConfigFactory` and passes 56 of its  [...]
 -| Faces 4.1 | Source reactor zip 4.1.2 | `faces` (Maven module) | **Runs: 
modern Arquillian modules (faces22/23/40/41) — 327 tests, 45 failures + 6 
errors** (2026-07-18) on Plume's Mojarra; the failsafe rerun mechanism inflates 
those totals, covering 10 distinct failing classes, all in 
`exclusions/faces.txt`. One is a TomEE product gap (faces-config.xml 
unmarshaller rejecting the nonstandard *https* `xsi:schemaLocation`, 
`Spec1760IT`); the rest are Mojarra/TomEE integration behaviors —  [...]
 +| Faces 4.1 | Source reactor zip 4.1.2 | `faces` (Maven module) | **Runs: 
modern Arquillian modules (faces22/23/40/41) plus the Chrome/Selenium 
`old-tck-selenium` modules (ajax, commandLink, protectedViews) — 298 tests, 0 
failures, 0 errors, 17 skipped** on Plume's Mojarra, with 
`exclusions/faces.txt` applied. The 10 excluded classes are one TomEE product 
gap (faces-config.xml unmarshaller rejecting the nonstandard *https* 
`xsi:schemaLocation`, `Spec1760IT`) and Mojarra/TomEE integratio [...]
  | Faces 4.1 (legacy old-tck) | Source reactor zip 4.1.2 (old-tck built from 
bundled sources) | `faces-old` (Maven module) | **Passes 5,391/5,391 
(standalone mode, no exclusions)** (2026-07-18). The recorded full run shows 5 
failures in `htmloutcometargetbutton`, all from a foreign server answering port 
8080 mid-run; they pass on re-run against TomEE. The JavaTest half deploys 
through the TCK's own `tomcat` handler (WAR copy into `webapps/`) against a 
TomEE instance the runner provisions [...]
  | JSON Processing 2.1 | `jakarta.json:jakarta.json-tck-*:2.1.1` (Maven 
Central; byte-identical to the EFTL zip pinned in `environment/versions.env`) | 
`jsonp` | **Passes 197/197** (2026-07-18) against Apache Johnzon 2.1.0, the 
JSON-P provider bundled in the TomEE Plume snapshot: 179 functional + signature 
tests and 18 pluggability tests. The signature test checks the `jakarta.json` 
packages of the distribution's `jakartaee-api` jar |
  | JSON Binding 3.0 | `jakarta.json.bind:jakarta.json.bind-tck:3.0.0` (Maven 
Central; byte-identical to the EFTL zip pinned in `environment/versions.env`) | 
`jsonb` | **Runs: 295 tests, 1 failure, 1 error, 5 skipped** against Apache 
Johnzon 2.1.0 with OpenWebBeans as the CDI SE container (the runner boots it 
because the TCK's own private `@BeforeAll` bootstrap is ignored by JUnit). The 
runner sets 
`johnzon.use-bigdecimal-stringadapter=false`/`johnzon.use-biginteger-stringadapter=false`
 ( [...]

Reply via email to