You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by ju...@apache.org on 2026/07/19 21:17:43 UTC
(tomee-tck) branch ee11 updated (2311593 -> 9a893bb)
This is an automated email from the ASF dual-hosted git repository.
jungm pushed a change to branch ee11
in repository https://gitbox.apache.org/repos/asf/tomee-tck.git
from 2311593 Surface JavaTest suite results as JUnit XML for CI ingestion
new 1fedb29 Keep the skipEJB modules out of the authentication invoker run
new 9a893bb Build the old-tck bundles without the native zip binary
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
runner-standalone/README.md | 2 +-
runner-standalone/authentication/pom.xml | 10 ++++++----
runner-standalone/faces-old/pom.xml | 16 ++++++++++++++++
runner-standalone/security-old/pom.xml | 16 ++++++++++++++++
4 files changed, 39 insertions(+), 5 deletions(-)
(tomee-tck) 01/02: Keep the skipEJB modules out of the authentication invoker run
Posted by ju...@apache.org.
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 <ju...@apache.org>
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>
(tomee-tck) 02/02: Build the old-tck bundles without the native zip binary
Posted by ju...@apache.org.
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 9a893bb6af0d9b7f522775e3de94248789613ed1
Author: Markus Jung <ju...@apache.org>
AuthorDate: Sun Jul 19 23:17:38 2026 +0200
Build the old-tck bundles without the native zip binary
The CI containers ship no zip executable, so the old-tck source build died
packaging its bundle. The download step now patches the release build to
take its portable ant <zip> fallback on every platform, and fixes that
fallback's includes pattern to recurse into the bundle directory (it
matched only the directory entry, producing an empty zip). Verified by
rebuilding the security-old bundle inside the pinned zip-less container:
21 MB, 1,490 files, same as the native-zip original.
---
runner-standalone/faces-old/pom.xml | 16 ++++++++++++++++
runner-standalone/security-old/pom.xml | 16 ++++++++++++++++
2 files changed, 32 insertions(+)
diff --git a/runner-standalone/faces-old/pom.xml b/runner-standalone/faces-old/pom.xml
index 221fa63..9b9a644 100644
--- a/runner-standalone/faces-old/pom.xml
+++ b/runner-standalone/faces-old/pom.xml
@@ -125,6 +125,22 @@
<!-- The build script invokes a bare `mvn`; route it through
the repository's Maven wrapper instead. -->
<replace file="${oldtck.source.dir}/docker/build_oldtck.sh" token="mvn -f" value=""$MVNW" -f"/>
+ <!-- The bundle packaging execs the native zip binary on unix
+ platforms, and the CI containers ship none. Renaming the
+ platform condition's property steers the build onto its
+ portable ant <zip> fallback (-ant-zip). The native path
+ additionally chmods unix.sh inside the bundle, but the
+ bundle is consumed via ant <unzip>, which drops
+ permissions anyway. -->
+ <replaceregexp file="${oldtck.source.dir}/release/tools/build.xml"
+ match="property *="isUnixPlatform""
+ replace="property="isUnixPlatformNativeZip""/>
+ <!-- The fallback's includes pattern matches only the bundle
+ directory entry itself, producing an empty zip; recurse
+ into its contents like the native `zip -r` did. -->
+ <replaceregexp file="${oldtck.source.dir}/release/tools/build.xml"
+ match="includes="(\$\{zip\.name\})""
+ replace="includes="\1/**""/>
<!-- Anchor the wrapper's multi-module root inside the TCK
sources so its path properties resolve against the TCK,
not this repository. -->
diff --git a/runner-standalone/security-old/pom.xml b/runner-standalone/security-old/pom.xml
index add8c72..b38dce0 100644
--- a/runner-standalone/security-old/pom.xml
+++ b/runner-standalone/security-old/pom.xml
@@ -168,6 +168,22 @@
<!-- The build script invokes a bare `mvn`; route it through
the repository's Maven wrapper instead. -->
<replace file="${oldtck.source.dir}/docker/build_oldtck.sh" token="mvn -f" value=""$MVNW" -f"/>
+ <!-- The bundle packaging execs the native zip binary on unix
+ platforms, and the CI containers ship none. Renaming the
+ platform condition's property steers the build onto its
+ portable ant <zip> fallback (-ant-zip). The native path
+ additionally chmods unix.sh inside the bundle, but the
+ bundle is consumed via ant <unzip>, which drops
+ permissions anyway. -->
+ <replaceregexp file="${oldtck.source.dir}/release/tools/build.xml"
+ match="property *="isUnixPlatform""
+ replace="property="isUnixPlatformNativeZip""/>
+ <!-- The fallback's includes pattern matches only the bundle
+ directory entry itself, producing an empty zip; recurse
+ into its contents like the native `zip -r` did. -->
+ <replaceregexp file="${oldtck.source.dir}/release/tools/build.xml"
+ match="includes="(\$\{zip\.name\})""
+ replace="includes="\1/**""/>
<!-- Anchor the wrapper's multi-module root inside the TCK
sources so its path properties resolve against the TCK,
not this repository. -->