Skip to content

TOMEE-4733 - Use surefire.version in MicroProfile TCK modules - #3156

Merged
jungm merged 1 commit into
mainfrom
TOMEE-4733-mp-tck-main
Nov 2, 2026
Merged

jungm merged 1 commit into
mainfrom
TOMEE-4733-mp-tck-main

Conversation

@jungm

@jungm jungm commented Nov 2, 2026

Copy link
Copy Markdown
Member

Follow-up to #3154. The MicroProfile TCK poms hard-code <version>3.6.1</version> for Surefire, so the 3.5.6 pin in tck/pom.xml doesn't apply to them. Config and JWT TCK still run Surefire 3.6.1 and fail with Parameter "suiteXmlFiles" is not supported since 3.6.0.

Failing build: https://ci-builds.apache.org/job/Tomee/view/tomee-11.x/job/master-build-full/2341/

This switches the hard-coded versions to ${surefire.version}. Checked locally that all MicroProfile TCK modules resolve to 3.5.6 and that Config/JWT get through surefire:test (no TCK tests run).

Jira: https://issues.apache.org/jira/browse/TOMEE-4733

🤖 Generated with Claude Code

The MicroProfile TCK poms hard-code the Surefire version, so the 3.5.6
pin in tck/pom.xml does not apply to them. Config and JWT TCK still run
Surefire 3.6.1 and fail on suiteXmlFiles.
@jungm
jungm merged commit f09a2c7 into main Nov 2, 2026
1 check passed
@jungm
jungm deleted the TOMEE-4733-mp-tck-main branch November 2, 2026 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant