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 1fedb2930aff1107f17cb42ae5e30e66b17663da
Author: Markus Jung <[email protected]>
AuthorDate: Sun Jul 19 23:16:22 2026 +0200

    Keep the skipEJB modules out of the authentication invoker run
    
    The tomee-remote profile sets skipEJB=true for the Web Profile run, so
    async-authentication and invoke-ejb-cdi built test-skipped wars that
    verify-invoker-result rejected as silently green - the same reason
    ejb-propagation and ejb-register-session were never included. Verified
    end-to-end: all 11 invoker projects pass, 0 failures, 0 errors.
---
 runner-standalone/README.md              |  2 +-
 runner-standalone/authentication/pom.xml | 10 ++++++----
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/runner-standalone/README.md b/runner-standalone/README.md
index 4748227..d5405c7 100644
--- a/runner-standalone/README.md
+++ b/runner-standalone/README.md
@@ -76,7 +76,7 @@ derived from; with the default exclusions applied these 
suites run green.
 | 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 (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 int [...]
-| 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 5 [...]
+| Authentication 3.1 | Source reactor zip 3.1.2 | `authentication` (Maven 
module) | **Runs: 10 Web Profile modules plus the signature test; green with 
the reviewed exclusions (all 11 invoker projects pass, 0 failures)**. 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 57 assertions; the runner patches [...]
 | 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 integration [...]
 | 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 |
diff --git a/runner-standalone/authentication/pom.xml 
b/runner-standalone/authentication/pom.xml
index c2e155b..b1ad3af 100644
--- a/runner-standalone/authentication/pom.xml
+++ b/runner-standalone/authentication/pom.xml
@@ -200,11 +200,9 @@
                 <argument>lifecycle</argument>
                 <argument>wrapping</argument>
                 <argument>register-session</argument>
-                <argument>async-authentication</argument>
                 <argument>status-codes</argument>
                 <argument>dispatching</argument>
                 <argument>dispatching-jsf-cdi</argument>
-                <argument>invoke-ejb-cdi</argument>
                 <argument>spi</argument>
                 <argument>authentication-signaturetest</argument>
               </arguments>
@@ -240,6 +238,12 @@
                 
<surefire.excludesFile>${tck.exclusions.file}</surefire.excludesFile>
                 
<failsafe.excludesFile>${tck.exclusions.file}</failsafe.excludesFile>
               </properties>
+              <!-- The EJB-dependent modules (async-authentication,
+                   invoke-ejb-cdi, ejb-propagation, ejb-register-session)
+                   stay out: the tomee-remote profile sets skipEJB=true for
+                   the Web Profile run, so including them only builds
+                   test-skipped wars that the verification step then rejects
+                   as silently green. -->
               <pomIncludes>
                 <pomInclude>basic-authentication/pom.xml</pomInclude>
                 <pomInclude>custom-principal/pom.xml</pomInclude>
@@ -247,11 +251,9 @@
                 <pomInclude>lifecycle/pom.xml</pomInclude>
                 <pomInclude>wrapping/pom.xml</pomInclude>
                 <pomInclude>register-session/pom.xml</pomInclude>
-                <pomInclude>async-authentication/pom.xml</pomInclude>
                 <pomInclude>status-codes/pom.xml</pomInclude>
                 <pomInclude>dispatching/pom.xml</pomInclude>
                 <pomInclude>dispatching-jsf-cdi/pom.xml</pomInclude>
-                <pomInclude>invoke-ejb-cdi/pom.xml</pomInclude>
                 <pomInclude>spi/pom.xml</pomInclude>
                 <pomInclude>authentication-signaturetest/pom.xml</pomInclude>
               </pomIncludes>

Reply via email to