Visitar URL original
[#108] Upgrade maven-surefire-plugin to 3.6.1 and fail when no tests run by rhusar · Pull Request #109 · wildfly/wildfly-launcher · GitHub
Skip to content

[#108] Upgrade maven-surefire-plugin to 3.6.1 and fail when no tests run - #109

Merged
rhusar merged 1 commit into
wildfly:mainfrom
rhusar:108-fix-new-jvm-test-reruns
Nov 5, 2026
Merged

rhusar merged 1 commit into
wildfly:mainfrom
rhusar:108-fix-new-jvm-test-reruns

Conversation

@rhusar

@rhusar rhusar commented Nov 5, 2026

Copy link
Copy Markdown
Member

Surefire 3.6.0 silently runs no tests in the new-jvm execution when test.java.home differs from the JDK running Maven, see apache/maven-surefire#3453. Override the version from jboss-parent with 3.6.1, which fixes it. Set the failIfNoTests property so that an execution running no tests fails the build, which can be overridden with -DfailIfNoTests=false. Code cleanup.

Fixes #108

… tests run

Surefire 3.6.0 silently runs no tests in the new-jvm execution when test.java.home differs from the JDK running Maven, see apache/maven-surefire#3453.
Override the version from jboss-parent with 3.6.1, which fixes it.
Set the failIfNoTests property so that an execution running no tests fails the build, which can be overridden with -DfailIfNoTests=false.
Code cleanup.

Signed-off-by: Radoslav Husar <rhusar@ibm.com>
final Path pathName = Path.of("path");
// Compare the message from the translation file to the message from the message interface
Assertions.assertEquals(String.format("WFLYLNCHR0001: " + properties.getProperty("pathDoesNotExist"), pathName),
Assertions.assertEquals(String.format(String.format("WFLYLNCHR0001: %s", properties.getProperty("pathDoesNotExist")), pathName),

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry about that, but this quiets the IDEs :)

@rhusar
rhusar merged commit 801474f into wildfly:main Nov 5, 2026
13 checks passed
@rhusar

rhusar commented Nov 5, 2026 •

Copy link
Copy Markdown
Member Author

Thanks @jamezp for the review!

@rhusar
rhusar deleted the 108-fix-new-jvm-test-reruns branch November 5, 2026 18:42
@rhusar

rhusar commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

OK, I believe the CI is now completely fixed, we can proceed with proper fixes :)

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.

new-jvm tests silently not run on non-default JDKs in CI

2 participants