[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209116#comment-17209116
]
Hudson commented on MNG-6985:
-----------------------------
Build failed in Jenkins: Maven » Maven TLP » maven »
MNG-6012-Missing-Profile-At-End #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/11/
> Incorrect value for maven.multiModuleProjectDirectory in integration tests
> --------------------------------------------------------------------------
>
> Key: MNG-6985
> URL: https://issues.apache.org/jira/browse/MNG-6985
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
> Reporter: Maarten Mulders
> Priority: Major
> Fix For: 3.7.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
