slachiewicz opened a new issue, #47: URL: https://github.com/apache/maven-executor/issues/47
### Affected version 1.0.0 with Maven 4.0.0-rc-6 ### Bug description `EmbeddedMavenExecutor` never returns when it runs Maven 4.0.0-rc-6 inside a Surefire or Failsafe forked test JVM. The same code with Maven 3.9.16 and 3.10.0-rc-1 completes normally. Observed on 2026-09-21 in three repositories that moved their integration tests from maven-verifier to maven-executor with `ExecutorHelper.forMavenInstallation(mavenHome, Mode.AUTO)` (no environment variables set, so `AUTO` selects embedded): - apache/maven-remote-resources-plugin#303: the first IT, `ITBadDependencyPoms`, starts at 10:15:37 and the job is cancelled at 10:44:27 with no further output ([run 35587231620](https://github.com/apache/maven-remote-resources-plugin/actions/runs/35587231620)). The same happens on all four `4.0.0-rc-6` cells (ubuntu and windows, JDK 21 and 25); the `3.9.x` and `3.10.0-rc-1` cells pass. - apache/maven-ear-plugin#556 and apache/maven-apache-resources#131: the same four cells, cancelled the same way. The last lines the embedded Maven 4 prints before the hang are the JLine native-access warnings from `org.jline.nativ.JLineNativeLoader` (`A restricted method in java.lang.System has been called ... Use --enable-native-access=ALL-UNNAMED`), then nothing. maven-verifier 2.0.0-M1 never embedded Maven 4 (its `Embedded3xLauncher` fails on `MavenCling` and falls back to forking), so these suites were green on Maven 4 before only because they forked. The three PRs now use `Mode.FORKED`, which passes. Not established: whether the hang is in `MavenCling`'s terminal setup when there is no console (the JLine warning is the last output), or in the executor's stream handling for Maven 4. A thread dump from a hung run would answer it; I can add one if useful. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
