[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665241#comment-15665241
]
Hudson commented on MNG-5889:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #18 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/18/])
MNG-5889 - adding logic that looks for the file argument and starts the
(hboutemy: rev da5b4df930925a0cbee95cfdca5c249ff143d91b)
* (edit) apache-maven/src/bin/mvn
* (edit) apache-maven/src/bin/mvn.cmd
> .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)
