[MSHARED-1015] Using Embedded3xLauncher fails with "-Dmaven.multiModuleProjectDirectory system property is not set"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-verifier-1.7.2
• Fix Version/s: maven-verifier-1.8.0
• Component/s: maven-verifier
• Assignee: Slawomir Jaranowski
• Reporter: Konrad Windszus
• Created: 04/Jan/22 08:55
• Updated: 08/Mar/22 20:19
• Resolved: 08/Mar/22 18:51

Description

When trying to use an embedded launcher created from the classpath (https://github.com/apache/maven-verifier/blob/17ebffa2467caa59f1e47c302ac03d9e00d8c314/src/main/java/org/apache/maven/it/Embedded3xLauncher.java#L124), launching fails with

-Dmaven.multiModuleProjectDirectory system property is not set

A similar issue was once reported and fixed for m2e at https://bugs.eclipse.org/bugs/show_bug.cgi?id=462944.

The reason is https://github.com/apache/maven/blob/706d9319f14b507f3c3deeba4eeda1a51a531c9b/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L351 which now requires this property to be set. This has been introduced by https://issues.apache.org/jira/browse/MNG-5767 in Maven 3.3.1

Issue Links

• relates to: MNG-5767 project-specific default jvm options and command line parameters
• links to: GitHub Pull Request #6