[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662297#comment-15662297
]
ASF GitHub Bot commented on MNG-5889:
-------------------------------------
Github user jvanzyl commented on the issue:
https://github.com/apache/maven/pull/94
Please do not change an existing test. The conditions under which this IT
passes should be left as-is and should continue running as it is in exactly the
form it runs now. Making purely additional logic is fine, or copy that IT and
make another test all together, do not change the logic or resources of the
existing IT. It captures behavior that is currently deployed in released
versions and so it should remain as a representation of that.
> .mvn directory should be picked when using --file
> -------------------------------------------------
>
> Key: MNG-5889
> URL: https://issues.apache.org/jira/browse/MNG-5889
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 3.3.3
> Reporter: Daniel Spilker
> Assignee: Tibor Digana
> Fix For: 3.4.0
>
>
> The {{.mvn}} directory is not picked up when using the {{--file}} switch to
> build a project from outside of the multi-module root.
> Example:
> * the module root is {{/foo/bar}}
> * {{.mvn}} is located at {{/foo/bar/.mvn}}
> * current directory is {{/foo}}
> * Maven is invoked with {{mvn --file bar/module/pom.xml}}
> I would expect the {{.mvn}} directory detection to start at the directory of
> the POM selected by {{--file}} and then go through the parent directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
