[ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747169#comment-14747169 ]
Daniel Spilker commented on MNG-5889: ------------------------------------- Hi Arnaud, indeed I was running into this problem when using the [Jenkins Maven Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin]. It should be possible to add a "base directory" setting to that plugin so that the CI can change to the base directory before launching Maven, but I think it would be better to fix the problem at the root. > .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)