[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370074#comment-17370074
]
Michael Osipov commented on MNG-6985:
-
I have removed the fix versions because they do not apply to Maven Core ITs and
this issue has been solely applied to the ITs.
> 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
>Assignee: Maarten Mulders
>Priority: Major
>
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221939#comment-17221939
]
Hudson commented on MNG-6985:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6957 #8
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6957/8/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215061#comment-17215061
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215047#comment-17215047
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
MNG-6012-Missing-Profile-At-End #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215045#comment-17215045
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6554 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215041#comment-17215041
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-5567 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215018#comment-17215018
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6888 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6888/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215012#comment-17215012
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6550 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215007#comment-17215007
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6551 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214983#comment-17214983
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6555 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214978#comment-17214978
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214960#comment-17214960
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6552 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214930#comment-17214930
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6909 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6909/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209435#comment-17209435
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209157#comment-17209157
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » REMOVE_DEPRECATED #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/REMOVE_DEPRECATED/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209137#comment-17209137
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6829 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6829/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209134#comment-17209134
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6889 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209124#comment-17209124
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-5567 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209114#comment-17209114
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6548 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6548/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209106#comment-17209106
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6888 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6888/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209098#comment-17209098
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6554 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209094#comment-17209094
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209089#comment-17209089
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6550 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209085#comment-17209085
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6555 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209087#comment-17209087
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MODELTESTS_IMPROVEMENT #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209082#comment-17209082
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6551 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209080#comment-17209080
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6909 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6909/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209078#comment-17209078
]
Hudson commented on MNG-6985:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6552 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209072#comment-17209072
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » Bananeweizen-MNG-6907 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/Bananeweizen-MNG-6907/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209062#comment-17209062
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209052#comment-17209052
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6556 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209039#comment-17209039
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6512-build-11 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6512-build-11/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209028#comment-17209028
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6952 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6952/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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206732#comment-17206732
]
Hudson commented on MNG-6985:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6965 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6965/12/
> 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)
[jira] [Commented] (MNG-6985) Incorrect value for maven.multiModuleProjectDirectory in integration tests
[
https://issues.apache.org/jira/browse/MNG-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194168#comment-17194168
]
Hudson commented on MNG-6985:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #22
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/22/
> 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)
