[MNG-6985] Incorrect value for maven.multiModuleProjectDirectory in integration tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Integration Tests
• Assignee: Maarten Mulders
• Reporter: Maarten Mulders
• Created: 09/Sep/20 13:59
• Updated: 26/Jun/21 21:40
• Resolved: 11/Sep/20 06:58

Description

The newVerifier() method in AbstractMavenIntegrationTestCase creates a System Property maven.multiModuleProjectDirectory and assigns the value of the basedir. That argument is passed in from the integration test and refers to the directory where the Maven invocation takes place (in Forked mode) or where it is simulated to take place (in Embedded mode).

For the majority of the cases, this is a valid assumption. However, if the test is supposed to run in a child module of a multi-module project, this assumption does not hold. Instead, the value of this System Property should be determined in the same way as the mvn / mvn.cmd scripts do: by traversing up the file system until a .mvn directory is located.

Issue Links

• links to: GitHub Pull Request #72