[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15661787#comment-15661787
]
ASF GitHub Bot commented on MNG-5889:
-------------------------------------
Github user rpatrick00 commented on the issue:
https://github.com/apache/maven/pull/94
@michael-o, while I have no problem contributing, I have no familiarity
with the maven-integration-test project so it will likely take me some time to
reverse engineer it enough to figure out how to create an integration test for
the shell scripts and the various use cases that should be tested. I would
hate to see this fix gated by the requirement for me to accomplish this given
the demands of my day job...
> .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)
