[ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493233#comment-15493233 ]
ASF GitHub Bot commented on MNG-5889: ------------------------------------- Github user Tibor17 commented on the issue: https://github.com/apache/maven/pull/93 IIUC this might be useful in CI because you may run `mvn deploy -f /path/to/project/pom.xml` and the discovery would be made in `/path/to/project/.mvn` as well. AFAIK Maven is not 2 processes running but one and you need to pass jvm options like this then. > .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 > > 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)