ascheman commented on issue #3345: URL: https://github.com/apache/maven-surefire/issues/3345#issuecomment-5011201829
@desruisseaux — the PR is finally up: #3392 implements the Module Source Hierarchy support (nested `target/classes/<module>/` detection, nested test-class scanning, and consumption of the compiler-generated `module-info-patch.args`), including two ITs: the classic `--patch-module` whitebox layout and a model-4.1.0 module source hierarchy fixture with `module-info-patch.maven`. Compared to the April proof of concept it additionally fixes a latent parser bug — the compiler writes `module-info-patch.args` with option and value on the *same* line, while the PoC assumed the two-line argfile form and could swallow an `--add-exports` directly following a skipped option — and it was verified against Maven 3.9.16, 3.10.0-rc-1, 4.0.0-rc-5 and the current 4.0.x-SNAPSHOT (rc-6 candidate). Scope of #3392 is one Java module per POM. Support for *several* modules per POM (`<build><sources>` with multiple `<module>` entries) is already implemented on a follow-up branch — verified against a real three-module component (602 tests, zero-config, one surefire execution) — and will arrive as a dedicated issue plus a stacked draft PR shortly. -- 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]
